Skip to main content
Glama

Tresca

Get a listing's facts

get_listing
Read-onlyIdempotent

Every fact Tresca holds for one MCP server or skill: what it does, capabilities, limitations, connection (drives the running app, files only, cloud API or documentation only), whether it can change models, operating systems, supported tool versions, licence, AI clients documented, official evidence, GitHub activity, sources and checked date. A loose name that matches nothing exactly returns suggestions.

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
listingYesTresca listing URL, slug, name or repository URL

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious trait beyond that: a loose name that matches nothing exactly returns suggestions rather than erroring, which tells the agent how to recover from a miss. It does not describe error behavior for ambiguous or disallowed inputs, and much of the field list merely restates the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-sentence catalog of returned fields is front-loaded but bloated, since an output schema exists and already defines those fields; enumerating 'licence, AI clients documented, official evidence, GitHub activity, sources and checked date' spends length without adding call guidance. The genuinely useful sentence about suggestion fallback is buried at the end.

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 does not need to explain return values, and it correctly focuses on what the record covers plus the fuzzy-match fallback. The remaining gap is routing guidance relative to the sibling lookup and search tools, which matters for an agent choosing among five related tools.

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 coverage is 100% with a single required parameter, so the schema already documents that it accepts a URL, slug, name, or repository URL. The description adds only the tolerance rule (loose names are accepted and fuzzy misses yield suggestions) and says nothing about how the four accepted forms are resolved or which takes precedence. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 and scope: every stored fact for exactly one MCP server or skill, and enumerates the dimensions covered (capabilities, connection mode, OS support, licence, evidence). An agent can tell this is a single-record lookup rather than a search, though it never names the sibling tools (search_listings, get_tool) it differs from.

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 only implied: the phrasing 'for one MCP server or skill' and the note that a loose name with no exact match returns suggestions suggest calling this when you already have a name, slug, or URL. There is no explicit statement of when to prefer this over search_listings or get_tool, and no mention of what to do when the lookup misses entirely.

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.