Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

get_tag

Read-only

One tag: its metadata, neighbor tags, and a top sample of its providers and APIs (with totals). provider_count counts companies that classify THEMSELVES here; api_provider_count counts the ones reached only through an API or operation tag — the two are disjoint, and a tag with no providers and many APIs names a resource, not a market. age summarises when the members were created (created_last_30d/90d, the largest same-day batch, and how much of the first page by composite is under 30 days old) — a high first_page share means the top of the tag is new listings, and find_providers(tags, sort:"created") lists them newest first. Use find_apis?tags=slug / find_providers?tags=slug for the full ranked list, or view=full here. 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
slugYesTag slug, as find_tags returns it, e.g. "payments".
viewNosummary (default, lean) or full.summary
limitNoTop members to show per list.
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: +"Tag slug, as find_tags returns it, e.g. \"payments\"."
  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
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 25,
+  "description": "Top members to show per list.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • 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. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false, but the description adds real semantics: that provider_count and api_provider_count are disjoint sets, that a tag with many APIs and no providers 'names a resource, not a market', and how `age` is computed. It does not cover caching, limits beyond the schema, or error behavior, but it materially exceeds what the annotations convey.

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?

Front-loads what the tool returns, then semantics, then alternatives. Dense and backtick-heavy, but every sentence carries information; a short 170-word blob for a tool with five parameters and no output schema is defensible, though it verges on overpacked.

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?

With no output schema, the description fully carries the return-value burden: it explains provider_count, api_provider_count, the age breakdown fields, the `next` sub-resource block, and where to get full ranked lists. Nothing an agent needs in order to call or interpret this correctly is missing.

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 description coverage is 100%, so the baseline is 3; the description goes beyond it by explaining what view='full' yields and clarifying that include_next=false suppresses the computed `next` affordance. It says nothing extra about `context` or `limit`, keeping it above but not at a maximum.

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?

Opens with a specific resource and its exact payload: 'One tag: its metadata, neighbor tags, and a top sample of its providers and APIs (with totals).' It is immediately separable from the many find_* siblings because it is a single-entity fetch and it names the list-oriented alternatives (find_apis, find_providers) itself.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use find_apis?tags=slug / find_providers?tags=slug for the full ranked list, or view=full here', and points to find_providers(tags, sort:"created") for a specific ordering need. It also tells the agent how to suppress the `next` block, so the choice space is fully covered.

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