Skip to main content
Glama
semlayer MCP server

semlayer MCP server

review_question

Read-onlyIdempotent

Retrieve one open review item by key to see its covered objects, claims, evidence, accept/reject impact, set verdict shape, and decision authority before answering or asking a user.

Instructions

Fetch one open review question in full, by its key.

    Call it after `review_questions` and before `review_answer`, or
    before putting a question to the user. It adds what the list leaves
    out: every object the question covers, each with where it is, the
    claim and the evidence; what accepting or rejecting would change;
    the shape a `set:` verdict takes; and who may decide.

    Read-only. A key that is not in the queue returns an `error` and
    what to do next -- an answered question has left the queue, which is
    usually what happened.
    

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": {
      "key": "<key>"
    },
    "name": "review_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe `key` of an open question, exactly as `review_questions` returned it.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / key / description
      Added value: +"The `key` of an open question, exactly as `review_questions` returned it."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, so the description is not required to restate safety. It does add real value beyond them: what payload comes back (covered objects with location, claim, evidence, accept/reject consequences, `set:` verdict shape, who may decide) and the failure mode for stale or answered keys. It stops short of describing pagination or size limits, which matters less for a single-record fetch.

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?

Front-loaded with the core action and the call-ordering constraint, then the payload rationale, then the error case. The middle clause enumerates several return fields at some length, but each item tells the caller why the call is worth making.

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?

For a single-key lookup with an output schema, the description covers action, ordering, payload value, and the error path. An agent has everything needed to call it at the right moment and interpret a failure.

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?

With one parameter at 100% schema coverage, the schema already documents `key` as 'exactly as `review_questions` returned it.' The description repeats the same provenance constraint rather than adding syntax, case sensitivity, or format detail, so this is the baseline case where the schema carries the meaning.

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?

States a specific verb and resource with scope: 'Fetch one open review question in full, by its key.' The singular 'one' and 'open' distinguish it cleanly from the sibling list tool review_questions and from review_answer.

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

Usage Guidelines5/5

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

Explicit ordering guidance is given: call it after `review_questions` and before `review_answer`, or before putting a question to the user. It also names the alternative outcome path -- a key not in the queue returns an `error` because an answered question has left the queue.

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