io.github.WiliamRosa/cosmos-semantic

explain

Retrieves definitions, ownership, source systems, and logic for business metrics, rules, dimensions, teams, systems, or processes to clarify governed concepts without querying raw tables.

Instructions

Explain a metric, business rule, dimension, concept, team, system or process: definition, owner, source systems, processes and logic.

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

Input Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It describes the information the tool returns, but with an output schema present that content is already structured; the description says nothing about read-only safety, permissions, side effects, or rate limits. This leaves behavioral traits largely undisclosed.

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?

The description is a single front-loaded sentence with no filler, moving from the verb to entity types to returned aspects. The long enumeration is dense but each element contributes to scope; minor run-on quality keeps it from a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with an output schema, the description covers purpose and returned content, but it leaves the required parameter undocumented and provides no routing guidance against siblings. Those gaps matter more because there are no annotations to fill in behavior.

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

Parameters2/5

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

The sole parameter 'name' has 0% schema description coverage, and the description does not explain what value should be supplied—whether it is a metric name, concept name, team, etc., or what format it takes. Listing the explainable entity types gives only a weak implicit hint.

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 uses a specific verb ('Explain') and enumerates the resource types it covers, plus the aspects returned (definition, owner, source systems, processes and logic). It is clear what the tool does, though it does not explicitly contrast itself with siblings like search_concepts or query.

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

Usage Guidelines2/5

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

It implies that the tool is used when an explanation is needed, but gives no explicit when-to-use conditions, exclusions, or alternatives such as search_concepts for concept lookup or query for data retrieval. An agent must infer the routing decision.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server