Skip to main content
Glama

Retrieve cited passages

koskamo_search_passages
Read-onlyIdempotent

Search Koskamo datasets for candidate passages with source citations and document versions. Similarity scores rank matches and do not measure factual confidence.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe question or search string
top_kNoMaximum candidate passages to retrieve
datasetNoOptional dataset id or slug. Defaults to all public datasets.

Output Schema

NameRequiredDescriptionDefault
queryYes
degradedNoPresent only when a backend was unavailable and passages came from a keyword fallback; coverage may be partial
guidanceYesWhat returned passages and scores do and do not establish
passagesYes
assessmentYesCandidate availability only; does not assess whether the question is answered

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds genuinely non-obvious behavior: similarity scores rank matches but are not a measure of factual confidence, which directly shapes how an agent should interpret results, and it names the returned fields (citations, versions).

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?

Two sentences, zero filler, with the core capability front-loaded and the scoring caveat placed immediately after where it matters most.

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?

An output schema exists, so return values need not be explained, and the description covers purpose plus the key interpretation caveat. It could go slightly further by indicating whether retrieval is semantic or keyword-based and what happens when dataset is omitted, though the schema covers the latter.

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 description coverage is 100%, so query, top_k, and dataset are already documented in structured form. The description only echoes the notion of datasets and adds no syntax, format, or defaulting detail beyond the schema, which is the expected baseline.

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?

States a specific verb and resource: 'Search Koskamo datasets for candidate passages,' plus what comes back (source citations, document versions). This is clearly distinct from siblings such as koskamo_search_use_cases or koskamo_search_mcp_servers, though it does not explicitly name an alternative.

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?

The word 'candidate' implies this is a first-pass retrieval step, but there is no explicit guidance on when to call this versus following up with koskamo_get_document or koskamo_get_artifact, and no stated exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources