Skip to main content
Glama

Get a listing's facts

get_listing
Read-onlyIdempotent

All facts Kitbay holds for one MCP server or skill, each with its source URL and checked date: publisher, official, can change data, needs credentials, connection, licence, repository, packages, latest version, last commit, archived.

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": {
      "listing": "<listing>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoNeeded only when a server and a skill share the slug
listingYesKitbay listing URL or slug

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without help. The description adds genuine value by disclosing that every fact carries a source URL and checked date, signalling provenance/recency data in the response; it does not say what happens when a listing is unknown or how stale facts are handled.

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?

A single front-loaded sentence that identifies the resource first, then lists the returned facts with zero filler. The trailing field enumeration is dense but each item is informative; only slight tightening would improve it.

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?

For a read-only, idempotent lookup with a full output schema, complete annotations and 100% schema coverage, the description supplies what the agent needs: scope (one listing), content (enumerated facts) and provenance. The only gap is routing guidance versus discovery siblings, which is a minor omission for a tool this simple.

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?

Schema description coverage is 100%, and both the 'listing' slug/URL parameter and the 'type' enum discriminator are documented in the schema itself. The description mentions 'one MCP server or skill' but adds no format, resolution or ambiguity guidance beyond the schema, so the baseline 3 applies.

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 states a specific resource ('all facts Kitbay holds for one MCP server or skill') and enumerates the fact categories returned (publisher, licence, repository, packages, versions, archived status), which lets an agent distinguish it from list_categories or search_listings. It stops short of naming any sibling explicitly, so the differentiation is inferred from the content list 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?

Usage is implied by the phrase 'for one MCP server or skill' — this is a lookup for an already-identified listing, not a discovery tool. There is no explicit statement of when to prefer it over search_listings (to find a slug first) or get_install_config (to act on the result), and no mention of failure conditions for unknown slugs.

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.