MCP server for structural inspection of SideFX .geo/.bgeo cache files with bounded resource limits
Two tools with complete input schemas and reasonable descriptions. Both tools follow verb_noun naming (inspect_cache, list_cache_attributes) and declare READ_ONLY risk. However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs. the other. Parameter descriptions are minimal (e.g., 'Path to the cache file to inspect' lacks format/constraint details). Output schemas are not documented in the tool definitions, the code shows CacheInspection and AttributeSummary dataclasses, but these are not exposed in the MCP tool registration. No error handling guidance visible in tool definitions. Security is sound (READ_ONLY, bounded resource limits), but descriptions don't explain the resource limits' purpose or when they matter.
Structural cache inspection with bounded resource limits
List attributes from a cache file with bounded resource limits
Output schemas not documented in tool definitions. Code shows CacheInspection and AttributeSummary dataclasses, but MCP tool registration does not expose return type schemas. LLMs cannot plan downstream operations or extract fields without documented output structure.
Descriptions lack LLM-optimized guidance on tool selection. Both tools inspect cache files but descriptions do not explain when to use inspect_cache (full structural analysis) vs list_cache_attributes (attribute summary only). LLMs will struggle to choose between them.
Parameter descriptions lack constraint details. 'Path to the cache file to inspect' does not specify: file format (.geo/.bgeo only?), absolute vs relative paths, or what happens if the file doesn't exist. 'Maximum file size in bytes' does not explain why these limits exist or what error occurs if exceeded.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
No error handling guidance in tool definitions. Code raises BgeoParseError, UnsupportedFormatError, and ResourceLimitError, but tool descriptions do not tell LLMs what to do if these occur (e.g., 'If file is malformed, try list_cache_attributes for a safer inspection').
Transport mechanism unknown. Repository does not show MCP server initialization, transport binding, or tool registration code. Cannot verify if this is STDIO, HTTP, or SSE-based.