Skip to main content
Glama

Look up a tool

get_tool
Read-onlyIdempotent

Is there an MCP server or skill for a tool (e.g. Figma, Blender, Notion), and is one official? Returns the tool's counts, its official listings and its Kitbay page, or suggestions when Kitbay does not cover it.

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": {
      "tool": "<tool>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool slug or name, e.g. "figma", "Google Sheets"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavior: it discloses the returned composition (counts, official listings, Kitbay page) and, importantly, the fallback path — suggestions are returned when Kitbay does not cover the tool. Rate limits and error behavior are unstated, which keeps it from a 5.

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?

One front-loaded sentence states the question first, then the return payload and the fallback, with a parenthetical example list that earns its place. Slightly dense phrasing ('its counts, its official listings and its Kitbay page') but no wasted sentences.

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 an output schema present, the description need not enumerate return fields, yet it still summarizes the shape and the no-match branch. For a one-parameter read lookup with full annotation coverage, an agent has everything needed to call it correctly; only explicit sibling routing is missing.

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

Parameters3/5

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

The single parameter is fully documented in the schema (min/max length, 'Tool slug or name, e.g. "figma", "Google Sheets"'), so 100% coverage sets the baseline at 3. The description's own examples (Figma, Blender, Notion) reinforce that common product names work, but add no syntax or format detail beyond 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?

The description frames a specific question the tool answers ('Is there an MCP server or skill for a tool... and is one official?') and names what comes back (counts, official listings, Kitbay page, suggestions). The resource is concrete ('a tool' keyed by slug or name), making it distinguishable from listing-level siblings, though it never names those siblings explicitly.

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?

Usage is implied by the framing question: use it when you want to know whether a given tool has an MCP server/skill and whether any listing is official. There is no explicit statement of when to prefer search_listings or get_listing instead, and no exclusions or prerequisites, so routing is left to inference.

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.