Skip to main content
Glama

get_threshold_scan

Retrieves a run's threshold scan table, enabling comparison of SII and silhouette scores to select the threshold that maximizes SII for clustered papers and communities.

Instructions

Threshold scan table: threshold, silhouette, clustered papers, SII, number of communities and edges. The best threshold maximises SII.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_threshold_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not state that this is a read-only retrieval, that the run must already have been analysed, or what happens with an invalid run_id. It only lists result columns, which the output schema already covers, so almost no behavior beyond the structured data is disclosed.

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?

Two compact sentences, front-loaded with what the table contains and followed by the selection rule. The column list is terse and the acronym SII is left undefined, but nothing is padding.

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

Completeness2/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-field detail is legitimately delegated, but for a run-scoped retrieval tool the description still omits the meaning of run_id and any precondition that the run has a computed threshold scan. Given zero annotation and zero schema coverage, an agent lacks the information needed to call this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter run_id is never referenced in the description. The agent gets no confirmation that run_id identifies a run (e.g. from list_runs) or whether it must be a completed analysis run, so the description does not compensate for the schema 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 resource (the threshold scan table) and enumerates the fields it contains (threshold, silhouette, clustered papers, SII, communities, edges), so an agent knows exactly what data this returns. It stops short of an explicit verb and never contrasts itself with siblings, but the content is distinctive enough to be told apart from tools like get_community or get_knowledge_tree.

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?

There is no when-to-use statement and no mention of alternatives or prerequisites. The line 'The best threshold maximises SII' gives an interpretation rule for the result rather than guidance on when to call the tool, leaving the agent to infer that this is the lookup for choosing a clustering threshold.

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