Skip to main content
Glama
justinmclean

Podlings MCP

by justinmclean

graduation_time_over_time

Compute yearly mean incubation time for graduated Apache podlings, filtered by sponsor type and date range, to track graduation trends.

Instructions

Return yearly average incubation time for graduated podlings based on start and end dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoHTTPS URL or local path to podlings.xml
sponsor_typeNoOptional sponsor type filter, defaults to incubator: incubator, project, or unknown
start_yearNoOptional inclusive start year filter
end_yearNoOptional inclusive end year filter
Behavior3/5

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

No annotations are provided; the description adds context by stating it returns yearly averages based on start and end dates, but lacks details on data handling, such as what happens with missing years or how incubation time is computed.

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 that is front-loaded with the core purpose, containing zero unnecessary words.

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

Completeness3/5

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

No output schema exists, yet the description does not specify the return format (e.g., units of time, structure). It is adequate for a simple aggregation tool but leaves some ambiguity.

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?

Input schema covers 100% of parameters with descriptions; the description reinforces that start and end dates are used but adds minimal new meaning beyond the 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?

Description clearly states 'Return yearly average incubation time for graduated podlings' with a specific verb and resource, distinguishing it from siblings like 'graduation_rate_over_time' which focuses on rates.

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?

The description implies usage for obtaining average incubation time but provides no explicit guidance on when to use this tool versus alternatives like 'graduation_rate_over_time' or 'completed_podlings_by_year'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/justinmclean/PodlingsMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server