Skip to main content
Glama
Sign In
Preflight

Preflight

by dainidude
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

preflight_pricing

Retrieve Preflight service information and its price list at no cost. Use it to review available security scan offerings and costs before making paid calls.

Instructions

Return the Preflight service info and price list (free).

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": "preflight_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. "Return" implies a read-only fetch, and "(free)" discloses that the call has no cost, which is genuinely useful context. However, it does not state whether the call has side effects, whether results are cached or time-sensitive, or anything about the response beyond the output schema.

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?

One short sentence with the resource front-loaded and no filler. Every element, including the cost note, carries information.

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?

This is a zero-argument informational tool with an output schema, so return values need not be described. The description covers what is returned, that it is free, and that it is read-only. Only the absence of guidance on when to prefer it over the sibling tools keeps it from a 5.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there are no argument semantics to explain. The description correctly implies a parameterless call by describing a single fixed resource.

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 a specific verb and resource: "Return the Preflight service info and price list." That is enough to distinguish it from the action-oriented siblings (preflight_check, preflight_sim, preflight_token_risk), which do not return pricing or service metadata. It does not explicitly contrast itself with those siblings, so it falls short of a 5.

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?

There is no explicit statement of when to call this tool rather than the check or simulation tools; the usage is only implied by the informational nature of the resource. The note "(free)" gives a useful cost signal for deciding whether to call, but no prerequisites or exclusions are stated.

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