Skip to main content
Glama
Sign In
skosmos-mcp

skosmos-mcp

by jsilvanus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

labels

Retrieve all labels for a concept URI within a vocabulary, with optional language filtering.

Instructions

Get all labels for a concept URI 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": {
      "uri": "<uri>",
      "vocabulary": "<vocabulary>"
    },
    "name": "labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesConcept URI
langNoLanguage code
vocabularyYesVocabulary identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, but the description clearly indicates a read-only operation ('Get') with no side effects. It does not contradict annotations, and the behavior is transparent for a retrieval tool.

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?

A single, front-loaded sentence with no filler words. Every word is necessary and contributes to understanding the tool's purpose.

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?

For a simple retrieval tool with 3 well-documented parameters and no output schema, the description is adequate. It could optionally mention the return format, but this is not critical given the clarity of the operation.

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%, providing baseline of 3. The description adds meaning by explicitly linking 'uri' and 'vocabulary' as context, which goes beyond the schema's individual parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'labels' with context 'for a concept URI in a vocabulary', clearly distinguishing it from sibling tools like 'get_concept_label' which likely returns a single label.

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?

The description implies when to use (retrieve labels for a concept URI), but provides no guidance on alternatives like 'resolve_label' or when not to use this tool.

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