Calculate carbon emissions for a flight by providing departure and destination airports for each leg, with optional passenger count.
Estimate carbon emissions for a flight.
| Name | Required | Description | Default |
|---|---|---|---|
| legs | Yes | Array of flight legs with departure_airport and destination_airport | |
| passengers | No | ||
| api_key | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description does not disclose any behavioral traits beyond the basic purpose, such as data sources, assumptions, or whether it's a calculation or API call.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, no wasted words, but overly terse. Could be more informative without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, no detail on result format, no guidance on airport code format or api_key requirement. Incomplete for effective agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33% (only 'legs' has a description). The description adds no extra meaning beyond the schema; passengers and api_key lack any description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'estimate' and resource 'carbon emissions for a flight', clearly distinguishing from siblings like carbon_electricity_emissions and carbon_vehicle_emissions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when or when not to use this tool, nor any mention of alternatives. The description is purely declarative with no usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server