Skip to main content
Glama

Tresca

List disciplines and tools

list_disciplines
Read-onlyIdempotent

Tresca's engineering disciplines, the tools in each that have MCP servers or skills (with counts), and the slugs to pass as discipline to search_listings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_disciplines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and idempotency profile is fully covered. The description adds only content shape (counts, slugs) and nothing about freshness, caching, or ordering of the returned catalog. That is adequate but not rich beyond the structured fields.

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 dense sentence with no filler, and the most decision-relevant fact (the slugs feed search_listings) is placed at the end where it reads naturally as the punchline. It is a verbless fragment, which is slightly less scannable than a full sentence but costs 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?

With no parameters, an output schema present, and full annotation coverage, the description only needs to convey purpose and role in the workflow, both of which it does. An agent could call it correctly from this text; the only omission is any notion of how the catalog is ordered or how often it changes.

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 tool takes zero parameters, so there is no parameter semantics for the description to carry and the baseline would be 4. However, the description's parameter-adjacent content (the slug value consumed by search_listings) is really about output, which the output schema already documents, so it does not add unique parameter meaning.

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 names the exact resource (Tresca's engineering disciplines), the per-discipline payload (tools with MCP servers or skills, plus counts), and the key field returned (slugs). That is more than a restatement of the name and it implicitly separates this from get_tool/get_listing, though it never states a verb or explicitly contrasts the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete downstream use: the slugs are 'to pass as discipline to search_listings', which tells an agent this is a discovery step that feeds the search tool. It stops short of explicit when-not guidance or of naming any other alternative, so it is clear context rather than full routing logic.

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.