Skip to main content
Glama
Sign In
io.github.WiliamRosa/cosmos-semantic

io.github.WiliamRosa/cosmos-semantic

by WiliamRosa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_concepts

Search governed business glossary concepts by term or synonym to find definitions and usage guidance, helping agents use consistent metrics instead of querying raw tables.

Instructions

Search glossary concepts by term or synonym, and tell how to use them.

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

Input Schema

NameRequiredDescriptionDefault
textYes
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only search and suggests usage guidance is returned, but it does not disclose matching behavior, result ordering, pagination, or how the default limit affects results.

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 definition is a single front-loaded sentence with no wasted preamble. However, 'and tell how to use them' is vague and blends retrieval behavior with output content rather than clarifying either.

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

Completeness2/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 values need not be explained. Still, for a search tool with zero schema descriptions and no annotations, the description is too thin to cover matching semantics and limit behavior adequately.

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?

Schema description coverage is 0%. The description only loosely maps 'by term or synonym' to the required text parameter, and it says nothing about the limit parameter or its default of 5.

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 verb and resource: 'Search glossary concepts by term or synonym.' That distinguishes it from generic siblings like query and explain, although it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool instead of query, explain, or show_sql. The reader is not told whether this is for discovery, definition lookup, or reverse synonym lookup, and no exclusions are given.

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

Deploy Server

Other Tools