Skip to main content
Glama

Panel: where a value came from

value_source
Read-only

Trace which source tables and columns produced a specific result cell, including the query filters behind it. Use it to audit any value by pull ID, row, and column.

Instructions

The results panel asks where one value came from (its row position and column name): the source tables and columns behind it and the query's filters. App-only.

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": {
      "pull_id": "<pull_id>",
      "row": "<row>",
      "column": "<column>"
    },
    "name": "value_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowYes
columnYes
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds genuinely new information: what the answer contains (source tables and columns plus the query's filters), which matters because there is no output schema. The unexplained 'App-only' tag is the only opacity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with the subject ('where one value came from') before the supporting detail. The trailing 'App-only' fragment is terse to the point of ambiguity but costs almost nothing.

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?

For a three-parameter read-only tool with no output schema, the description does enough to convey purpose and result shape. It falls short on pull_id semantics and on what 'App-only' implies for a programmatic caller, which an agent may need before invoking it.

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 0%, so the description must carry parameter meaning. It clarifies row and column as 'row position' and 'column name', but pull_id — the parameter that identifies which query result is being interrogated — is never mentioned, leaving a real gap.

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 names a specific capability: tracing one cell's provenance back to source tables, columns, and query filters, keyed by row position and column name. That is clearly narrower than siblings like lineage or compare, though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: 'The results panel asks...' plus 'App-only' tells the agent this is a UI-driven drill-down on a specific cell. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as lineage for broader tracing.

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