Skip to main content
Glama

Tresca

Get install steps

get_install_steps
Read-onlyIdempotent

The install steps for one MCP server or skill, copied exactly from the project's own documentation, each with its source URL, plus warnings (archived, can change models, needs a licence). With client, only that client's steps plus the general ones (downloads, builds, packages). Show the user the steps and ask before running a command or editing a file.

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_install_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNoThe user's AI client, e.g. "Claude Desktop", "Claude Code", "Cursor"
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.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond that: content is copied exactly from the project's own documentation, each step carries its source URL, and warnings about archived projects, model changes, and licensing are surfaced. The only gap is what happens when the listing cannot be resolved.

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

Conciseness5/5

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

Three tightly packed sentences with no filler: content and provenance first, parameter behavior second, agent-handling instruction last. Every clause carries information the agent needs.

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 return-value shape need not be described, and the description still usefully names the warning categories and source URLs an agent will encounter. For a two-parameter read tool with full annotation coverage, this is nearly complete; only failure behavior for an unresolvable listing is unaddressed.

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, but the description adds genuine filtering semantics for `client` that the schema does not: only that client's steps plus the general ones (downloads, builds, packages). The `listing` parameter gains no extra meaning beyond the schema's 'URL, slug, name or repository URL'.

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 exactly what is returned: install steps for one MCP server or skill, copied verbatim from the project's documentation with source URLs and warnings (archived, model changes, licence). That is far more specific than the name alone and lets an agent distinguish it from listing/tool lookup siblings, though it does not explicitly name a contrasting sibling.

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 rather than stated: the `client` behavior ('only that client's steps plus the general ones') tells the agent how filtering works, and 'Show the user the steps and ask before running a command or editing a file' gives post-call handling guidance. There is no explicit when-to-use versus get_tool/get_listing or any stated exclusion condition.

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.