Skip to main content
Glama
Sign In
skosmos-mcp

skosmos-mcp

by jsilvanus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

concept_path

Retrieve the hierarchical path from a concept to its root via broader transitive relations in a SKOS vocabulary.

Instructions

Get the hierarchy path from a concept to its root via broader transitive relations

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": "concept_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesConcept URI
langNoLanguage code
vocabularyYesVocabulary identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description must disclose behaviors. It mentions 'via broader transitive relations' indicating upward traversal, but does not specify edge cases (e.g., no broader concepts), return format, or potential errors.

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, concise, front-loaded sentence with no wasted words.

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?

With no output schema, the description should clarify the return value (e.g., list of URIs or labels). It only mentions 'hierarchy path', leaving format ambiguous. Parameters are well-covered but no context on ordering or defaults.

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?

Input schema covers 100% of parameters with descriptions. The tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly specifies the action: 'Get the hierarchy path from a concept to its root via broader transitive relations'. It distinguishes from siblings like 'broader_concepts' (which likely returns immediate broader concepts) by emphasizing the transitive path to root.

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 this tool (to get the full hierarchy path), but does not explicitly state when not to use it or mention alternatives among the siblings like 'broader_concepts' for immediate parents.

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