install_snippets
Return ready-to-paste configuration snippets for installing this MCP server in Claude Code, Cursor, Cline, Continue.dev, Windsurf, and Zed. Free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Prism — Data Enrichment for AI Agents
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Full disclosure: returns ready-to-paste snippets, and states it's free. No annotations provided, but description covers behavior completely for a parameterless tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, 20 words, front-loaded with key information. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Describes output (snippets) and target IDEs. Could specify return format (e.g., object with keys per IDE), but sufficient for tool complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist; schema coverage is trivially 100%. Description adds value by explaining the tool's output beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'Return' and resource 'configuration snippets' for installing this MCP server in multiple IDEs. It clearly distinguishes from siblings like list_endpoints and pricing_info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly indicates usage for obtaining installation snippets, but lacks explicit when-to-use or comparisons to alternatives. For a simple tool, this is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation3/5
Most tools are clearly distinct, but list_endpoints and pricing_info both expose endpoint and pricing details, which could cause an agent to call the wrong one. install_snippets, usage_stats, and wallet_helper have separate, well-defined purposes.
Naming Consistency3/5
All names use lowercase snake_case, but the style is mixed: install_snippets and list_endpoints follow verb_noun, while pricing_info, usage_stats, and wallet_helper are noun-based. The naming is readable but not uniform.
Tool Count4/5
Five tools is a reasonable, compact set for an onboarding and payment-helper server. However, for a server branded as 'Data Enrichment', the count reflects meta-support tooling rather than actual enrichment capabilities.
Completeness2/5
The set covers installation, endpoint discovery, pricing, usage stats, and wallet setup, but it includes no actual data-enrichment operations. Given the stated purpose, agents cannot perform the primary task through these tools.