Skip to main content
Glama
Sign In
skosmos-mcp

skosmos-mcp

by jsilvanus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

resolve_label

Resolve a label text to identify matching concepts within a controlled vocabulary. Optionally filter by language for precise results.

Instructions

Resolve a label text to concepts in a vocabulary

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>",
      "vocabulary": "<vocabulary>"
    },
    "name": "resolve_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage code
textYesLabel text to resolve
vocabularyYesVocabulary identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should carry behavioral details, but it only states the function. Missing information on case sensitivity, exact vs fuzzy matching, multiple matches, or response format.

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?

The description is a single clear sentence with no wasted words. Every part is necessary for stating the core function.

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?

Given the tool's simplicity and lack of output schema, the description is too sparse. It omits important context like what 'resolve' entails (exact match? returns multiple concepts?), which would help the agent anticipate behavior.

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%, and the description adds minimal value beyond repeating parameter names. The baseline of 3 is appropriate because the schema already documents each parameter's 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 clearly states the verb 'resolve' and the resource 'a label text to concepts in a vocabulary', making the tool's purpose specific. However, it does not explicitly differentiate it from siblings like 'search_concepts' or 'autocomplete', though the action is distinct enough.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., search_concepts, autocomplete, get_concept). There are no when-not or alternative recommendations.

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