Loading ToolBench
Client library for auditing and rewriting product content to optimize for LLM citations and generative engine optimization
This server has significant definition quality gaps. Both tools have reasonable names starting with action verbs (analyze_, optimize_) and moderate descriptions (60-85 chars), but the schemas are incomplete and lack critical detail. Input parameters are present but descriptions are generic and lack validation guidance. Output schemas are entirely undocumented, there is no specification of what fields the agent should expect in responses, making downstream tool composition impossible. The mock mode implementation reveals internal logic (heuristic scoring, spec-density calculations) that should be abstracted from the LLM. Error handling is minimal, the GenerativeSeoError class exists but provides no recovery guidance. No parameter validation, no enum constraints, no pagination support. The server appears to be a prototype rather than production-grade.
Evaluate current copy and return a score indicating citation probability by AI search engines.
Optimize copy to satisfy LLM crawlers and output JSON-LD structured schema markup.
No output schema documented. Both tools return complex Dict[str, Any] with no specification of fields, types, or structure. Agent cannot reliably extract results or chain downstream calls.
Input parameters lack validation constraints. 'specs' parameter is type 'object' with no minProperties, maxProperties, or description of key-value structure. 'content' and 'original_copy' accept unbounded strings with no length limits or format guidance.
Parameter descriptions are generic and under 72 chars. 'content' → 'The product content/copy to analyze' (38 chars) provides no guidance on length, format, or expected structure. 'specs' → 'Dictionary of specification key-value pairs (e.g., Frequency Response, Battery Life)' includes example values that LLMs may reuse literally.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
No error handling or recovery guidance. GenerativeSeoError is raised for API failures but provides no actionable next steps. Mock mode silently falls back with heuristic results, agent cannot distinguish mock from real API responses.
Transport mechanism unknown. No evidence of HTTP, SSE, or STDIO implementation in provided code. Only a GenerativeSeoClient class with mock mode, actual MCP server registration, protocol transport, and request/response handling are not visible.
Tool composition broken. analyze_citability returns 'citability_score' (numeric), but optimize_content accepts 'original_copy' (string), no field alignment, no ability to pass citability result forward. Each tool operates independently with no chaining.