Skip to main content
Glama
Sign In

Mycel

by com.mycelhq
OverviewDiscussionsAdmin

get_deliverable

One deliverable: its versions, files, what was checked, and its timeline.

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": {
      "deliverable_id": "<deliverable_id>"
    },
    "name": "get_deliverable"
  }
}

Input Schema

NameRequiredDescriptionDefault
deliverable_idYesThe deliverable's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the return payload composition (versions, files, checks, timeline), which is genuinely useful and not derivable from the schema, but it says nothing about what happens for an unknown id, whether access is permission-gated, or how many versions are returned.

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?

A single short line with zero filler, front-loading the resource before the payload contents. It is a sentence fragment with no verb, which reads slightly telegraphic but wastes nothing.

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?

For a low-complexity read tool with one fully documented parameter and no output schema, the description covers the resource, its identifier, and the shape of what comes back. Only failure behavior and any access constraints are missing.

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?

A single parameter at 100% schema coverage, and the schema already says 'The deliverable's id.' The description adds no format, source, or provenance detail for that id, so it neither helps nor hurts beyond the schema baseline.

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

Purpose4/5

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

The description names the resource ('One deliverable') and enumerates the payload an agent gets back — versions, files, checks performed, timeline. The singular framing implicitly separates it from the sibling list_deliverables, though it never states a verb like 'retrieve' or 'fetch'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. An agent can infer that this is the detail view reached from a list, but that inference comes from the singular noun, not from stated guidance.

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

All Mycel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources