Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

get_provider_tools

Read-only

Every MCP tool a provider ships, with the operation each one wraps and its auth. Reports provenance per tool: first-party means the provider publishes that server, derived means API Evangelist generated a candidate tool list from their OpenAPI because no hosted server was found. Filter with provenance=first-party for a true picture — counting derived tools as the provider's own overstates MCP adoption badly. A server whose tools could not be enumerated (auth-gated) is reported in coverage.not_enumerable rather than silently counted as zero.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based (default 1).
slugYesProvider slug — lowercase, hyphenated, as find_providers returns it, e.g. "stripe".
limitNoResults per page, 1-100 (default 25).
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
provenanceNoRestrict by who authored the tool list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / slug / description
      Added value: +"Provider slug — lowercase, hyphenated, as find_providers returns it, e.g. \"stripe\"."
  3. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description goes further with behavior an agent could not infer: what first-party vs derived provenance means and that auth-gated servers land in coverage.not_enumerable instead of being silently zeroed. It does not cover pagination or return ordering.

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?

The core purpose is front-loaded, followed by provenance semantics and the auth-gated caveat, so the ordering is sensible. The middle sentence is dense and slightly long, but every clause carries information an agent needs to interpret results correctly.

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?

With no output schema, the description does useful work by sketching the return shape (tool, wrapped operation, auth, per-tool provenance, coverage.not_enumerable). That is close to sufficient for a read-only lookup, though it never mentions pagination behavior despite page/limit parameters.

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?

Schema coverage is 100%, so 3 is the baseline, but the description meaningfully enriches the provenance enum by defining both values, which the schema only labels as 'who authored the tool list.' The other four parameters (page, limit, slug, context) get no added explanation.

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?

States a specific resource and scope: every MCP tool a provider ships, plus the operation it wraps and its auth. It is clearly provider-scoped, which separates it in spirit from global searchers like find_mcp, but it never names a sibling to make that distinction explicit.

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

Usage Guidelines4/5

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

Gives concrete guidance on how to use the provenance filter ('filter with provenance=first-party for a true picture') and explains the cost of not doing so. It stops short of naming alternative tools such as find_mcp or get_provider_operations or stating when this tool is the wrong choice.

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

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources