Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_graphql_agent

Write GraphQL SDL schemas, resolvers, DataLoader, subscriptions, and federation config from plain-English requests. Specify a programming language (default Python) to generate backend-ready code.

Instructions

Write GraphQL SDL schemas, resolvers, DataLoader, subscriptions, and federation config.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timps_graphql_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestNoPlain-English task or context for the agent.
languageNoPrimary programming language (default: python).python

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Write,' implying creation, but does not mention side effects, required permissions, output format, or the agent's interactive nature. This is a significant gap for an agent that likely performs complex, multi-step operations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, action-oriented sentence that front-loads the core purpose. It is concise and avoids fluff, though it could be slightly more structured to list deliverables. Overall, it efficiently conveys the main function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (agent handling multiple GraphQL components), the description is incomplete. It lacks guidance on what constitutes a good 'request,' expected interactions, or output behavior. With no output schema or annotations, the description alone is insufficient for an agent to use this tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% since both 'request' and 'language' have descriptions in the schema. The tool description does not add any additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the verb 'Write' and specifies the resource as 'GraphQL SDL schemas, resolvers, DataLoader, subscriptions, and federation config.' This is specific and directly distinguishes it from sibling tools like generic web search or SQL optimizer, making its purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies usage for GraphQL development tasks, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or alternative recommendations. Given the many sibling tools, more guidance would be helpful, but the purpose alone implies the context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools