Skip to main content
Glama

Get one tag

get_tag
Read-onlyIdempotent

Returns one tag: count, median annualized revenue and members with rank and revenue. Example: {"slug":"vibe-coding"} -> every business tagged vibe-coding. Unknown slug -> isError. Cost: free (100 calls/day without a key).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTag slug (e.g. vibe-coding, cx, enterprise; see list_tags).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Tag slug (e.g. trustmrr, mcp, seo)."New value: +"Tag slug (e.g. vibe-coding, cx, enterprise; see list_tags)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: unknown slugs surface as isError rather than an empty result, and the cost model (free, 100 calls/day without a key) tells the agent about rate limiting — neither of which appears in the annotations.

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-loaded with the return shape, then the example, then the error and cost notes — every sentence carries information. It is dense to the point of being telegraphic ('Cost: free (100 calls/day without a key).'), which slightly hurts readability but wastes nothing.

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?

An output schema exists, so the description need not fully specify the response, and annotations carry the safety profile. Combined with the error behavior and quota note, an agent has enough to invoke correctly; the missing piece is guidance on obtaining valid slugs from list_tags.

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; the description earns the bump by clarifying what the slug resolves to semantically ('every business tagged vibe-coding'), which is more than the schema's plain 'Tag slug' label. It still does not point to list_tags for slug discovery, but that pointer is already in the schema.

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?

A specific verb and resource ('Returns one tag') plus a concrete inventory of what comes back (count, median annualized revenue, members with rank and revenue). It is clearly the single-tag counterpart to the list/leaderboard family, though the distinction from list_tags and get_category is left implicit rather than stated.

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?

The example ('{"slug":"vibe-coding"} -> every business tagged vibe-coding') shows what the input selects, and 'Unknown slug -> isError' defines the failure path. But there is no explicit statement of when to prefer this over list_tags or get_business, so usage is inferable rather than guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources