Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

get_provider

Read-only

Full detail for one provider: profile, rating, and the APIs it publishes. The heavy collections and common sections are omitted by default (their counts are still reported) — pass view=full for the whole document, or fields=["common"] for a section. Narrow for cheap reads: fields=["score"] returns just the rating. Relative artifact URLs are resolved to absolute, fetchable ones. Results carry next: the sub-resources that exist for this entity and the exact tool call that retrieves each, computed from this record. Pass include_next=false to omit it.

Input Schema

NameRequiredDescriptionDefault
slugYesProvider slug — lowercase, hyphenated, as find_providers returns it, e.g. "stripe".
viewNosummary (default, lean) or full.summary
fieldsNoReturn exactly these top-level keys (slug and name always included); overrides view.
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
include_nextNoSet false to omit the `next` affordance block.

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 / view / description
      Previous value: -"summary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity)."New value: +"summary (default, lean) or full."
  2. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • addedInput schema / properties / include_next
      Added value: +{
+  "default": true,
+  "description": "Set false to omit the `next` affordance block.",
+  "type": "boolean"
+}
  5. Changed2 schema fields changed
    • changedInput schema / properties / fields / description
      Previous value: -"Top-level keys to return; slug and name are always included. Omit for the default set (everything except collections and common). Use [\"all\"] for the complete document."New value: +"Return exactly these top-level keys (slug and name always included); overrides view."
    • addedInput schema / properties / view
      Added value: +{
+  "default": "summary",
+  "description": "summary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity).",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  6. Changed1 schema field changed
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Top-level keys to return; slug and name are always included. Omit for the default set (everything except collections and common). Use [\"all\"] for the complete document.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  7. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover only readOnly/openWorld; the description discloses the non-obvious behaviors: heavy `collections`/`common` sections omitted by default with counts preserved, relative artifact URLs rewritten to absolute fetchable ones, and a computed `next` block listing sub-resources and their exact tool calls. This is exactly the extra context annotations cannot carry.

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?

Dense but every sentence earns its place and the core purpose leads. It is on the long side, but no sentence is redundant with the schema or annotations.

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

Completeness5/5

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

No output schema exists, and the description compensates by explaining the default-vs-full payload shape, URL rewriting, and the `next` affordance (plus how to suppress it). For a single-entity read tool this is complete.

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 the baseline is 3, but the description adds real semantics: fields overrides view, the omitted heavy sections still report counts, include_next=false omits the affordance block, and context is never used to rank. That is meaning beyond the schema strings.

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?

States a specific verb and resource ('Full detail for one provider: profile, rating, and the APIs it publishes'), which clearly separates it from siblings like get_provider_rating, get_provider_apis, and find_providers. An agent can pick this without opening the schema.

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 selection guidance for the view/fields parameters ('pass view=full for the whole document', 'Narrow for cheap reads: fields=["score"]'). It does not explicitly name which sibling to use when only a rating is wanted, but the cost-oriented narrowing guidance implies the trade-off clearly.

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
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources