Skip to main content
Glama
semlayer MCP server

semlayer MCP server

review_decisions

Read-onlyIdempotent

Lists every verdict recorded in the loaded semantic layer and who made it so you can check what an answer rests on and identify unconfirmed agent decisions.

Instructions

List every verdict recorded in the loaded layer, and who made it.

    Call it when the user asks what has been decided or by whom, or to
    check what an answer rests on. Each row has the verdict, where it
    applies, the date, the name recorded and a `signal`. Read `signal`:
    `agent` means nobody has confirmed it. Say so when an answer rests
    on one.

    Read-only, and it covers the whole layer the session has loaded. For
    what is still undecided, call `review_questions`.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "review_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/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 the description correctly reinforces read-only while adding real context: coverage is the entire layer the session has loaded, and rows carry a `signal` field whose `agent` value means nobody has confirmed it, with an instruction to disclose that. That provenance caveat is genuinely useful behavior guidance beyond the annotations, though pagination/volume behavior for a whole-layer listing is not mentioned.

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?

Three short paragraphs, front-loaded with purpose, then trigger conditions, then behavioral caveats and the sibling pointer. Every sentence carries information an agent needs; no restatement of the name or filler.

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 zero-parameter, read-only listing tool with an output schema already defining the row shape, the description covers purpose, triggers, scope, sibling routing, and the one interpretive nuance (`signal`). Nothing essential to correct invocation is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. Nothing in the text misleads about inputs.

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 ('List every verdict recorded in the loaded layer, and who made it') plus an explicit scope (the whole loaded layer). It is clearly distinguishable from `review_questions`, which the description names as the tool for undecided items.

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?

Gives concrete trigger conditions ('when the user asks what has been decided or by whom, or to check what an answer rests on') and names the alternative for the complementary case ('For what is still undecided, call `review_questions`'). Both when-to-use and when-to-use-something-else are explicit.

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