Skip to main content
Glama

Feature Library

Get a runnable check

get_check
Read-only

Free. Scripts you run on your own build, in its page, for what a checklist can’t prove: layout-probe measures that nothing moves when the view changes state (column edges, row tops, controls that come and go) and that every focus ring shows whole. Without an id, the list with what each proves and how to run it; with an id, the script itself as text. Run them at every width you claim and pass the results to check({ evidence }).

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": "get_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional: the check id, e.g. layout-probe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-open-world operation. The description adds meaningful context: it is free, returns a list without an id, returns script text with an id, and should be followed by passing evidence to check.

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?

The definition is a dense but efficient paragraph that front-loads the purpose, explains the id-dependent behavior, and ends with the next step. The examples are relevant, though the first sentence is long.

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 low-complexity, one-parameter read-only retrieval tool with no output schema, the description covers the retrieval modes, what the scripts are for, and how to use their results. The annotations already cover safety, so no critical context 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 schema already documents the optional id and includes an example. The description adds useful conditional semantics: omitting id returns the list, while supplying id returns the script itself as text.

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 clearly states that this tool returns runnable check scripts, or a list when no id is supplied, and explains what layout-probe verifies. The resource is specific, though it does not explicitly contrast with sibling retrieval tools such as get_playbook or get_recipe.

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?

It says to use these checks for what a checklist cannot prove, run them at every claimed width, and pass the results to check({ evidence }). That gives clear operational context, but it does not state explicit exclusions or compare against other get_* siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources