Gantry

by fourn9

Overview Schema Source Related Servers Discussions Admin

Python

Local

product_overview

Read-only

Generate a concise product summary from basis and intent details to help agents understand scope and plan next steps.

Instructions

product overview

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`arguments`	Yes
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.0Nov 7, 2026

TDQS

D1.1/5.0

Behavior1/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description would only need to add context such as scope, auth, or result shape. It adds none - the two-word phrase conveys zero behavior beyond the structured hints, and does not contradict them.

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

Conciseness2/5

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

The text is short but that brevity reflects under-specification rather than efficiency. There is no front-loaded statement of purpose or scope to anchor the agent.

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

Completeness1/5

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

This is a nested-object, required-argument tool with no parameter documentation and no output schema, so the description bears the full explanatory burden - and supplies nothing. An agent cannot reasonably infer how to populate 'basis' or 'intent' from this definition.

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

Parameters1/5

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

Schema description coverage is 0% and both nested objects ('basis' and 'intent') have no documented fields or meaning. The description provides no compensating explanation, leaving an agent unable to know what to put in these structures.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'product overview' merely restates the tool name in slightly different casing. It names no verb, no resource scope, and does not distinguish the tool from siblings such as studio_overview, project_details, or context.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of alternatives, and no indication of what an agent should expect to get versus calling studio_overview or project_details.

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