Skip to main content
Glama

mcp-server

by com.quelvio

get_source_detail

Read-onlyIdempotent

Return per-chunk source provenance for a previous query — document path, lifecycle state, embedding timestamp, contributor, last-updated — useful for verifying a citation or surfacing trust signals to a downstream system. Pass a query_id returned by an earlier query_knowledge call. Returns 404 if the query_id is unknown OR belongs to a different tenant (indistinguishable to prevent info-leak). Zero Knowledge Tokens consumed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
query_idYesUUID returned in the structured-metadata block of a prior `query_knowledge` response. Tenant-scoped — cross-tenant 404.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description adds that zero Knowledge Tokens are consumed and that 404 is returned for unknown or cross-tenant query IDs (indistinguishable to prevent info-leak). This is valuable behavioral context.

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 two sentences: first explains purpose and output, second explains input and error behavior. No redundant information; every sentence is purposeful.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter and no output schema, the description covers input origin, output fields, error handling, and token consumption. It is complete for the tool's complexity.

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%, but the description adds meaningful context: query_id is a UUID from the structured-metadata block of a prior query_knowledge response, and that it is tenant-scoped. This augments the schema's description.

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 explicitly states it returns per-chunk source provenance for a previous query, listing specific fields (document path, lifecycle state, etc.). It clearly distinguishes from sibling tools (list_domains, query_knowledge) by focusing on provenance retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies to pass a query_id from a prior query_knowledge call, which is clear and actionable. It does not explicitly state when to avoid this tool, but the context of 'verifying a citation or surfacing trust signals' implies its use case.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool serves a distinct purpose: get_source_detail provides provenance for previous queries, list_domains lists available knowledge domains, and query_knowledge performs the actual search. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_source_detail, list_domains, query_knowledge. The naming is uniform and predictable.

Tool Count4/5

With only three tools, the set is minimal but well-scoped for a read-only knowledge query interface. It covers the essential workflow without unnecessary tools, though a few more (e.g., to list query history) could be beneficial.

Completeness4/5

The tools cover the core workflow: domain exploration (list_domains), knowledge querying (query_knowledge), and provenance retrieval (get_source_detail). Missing is a way to list past queries or manage the knowledge base, but these are outside the apparent intended scope.

Resources