Skip to main content
Glama

read_silicon_sample

Read-onlyIdempotent

Read LLM credentials, prompt guide, saved draft config, jobs, job status, results, or wait for completion.

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

Input Schema

NameRequiredDescriptionDefault
limitNoWith include results: rows per page (1–200, default 50).
cursorNoWith include results: the next_cursor from the previous page; omit for the first page.
job_idNoJob UUID for job/results/wait includes
includeNoDefaults to config when survey_id is set, else credentials
team_idNoWith include credentials: list only this workspace's saved LLM credentials.
survey_idNoSurvey UUID — required for config/jobs includes
timeout_secondsNoWith include wait: how long to wait for the job to finish before returning its current status (5–45 seconds, default 30).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely non-obvious behavior beyond that: the tool can block and 'wait for completion', which is not inferable from a read-only annotation set. It adds nothing on auth, pagination, or multi-include interaction, so a 3 fits.

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?

It is a single front-loaded sentence with no filler, which is efficient. The long inline list largely duplicates the enum values already in the schema, so it is not maximally economical but is not bloated either.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and all seven parameters carry full schema descriptions including required-ness for each include mode. What remains thin is how multiple include modes combine and what happens with the 'wait' mode's result, but that is a minor gap for an otherwise well-structured read tool.

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 100%, so the schema already documents limit, cursor, job_id, include, team_id, survey_id and timeout_seconds in detail. The description's enumeration of include values largely restates the enum and adds no syntax, default, or dependency guidance, making the baseline 3 appropriate.

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 verb ('Read') and enumerates the resources it can retrieve (credentials, prompt guide, config, jobs, job status, results), so an agent can tell what it returns. However, it never distinguishes this tool's role from edit_silicon_sample or the read_survey/read_responses family, leaving the multi-mode scope implicit.

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 or when-not-to-use guidance beyond the bare resource list. The description does not explain how to choose among the seven include modes, nor when an agent should call this instead of a sibling reader.

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