Skip to main content
Glama

ai_modeling_runtime_status

Read-only

Verifies pinned Studio frontend JS/WASM files in the private cache or a chosen source_dir, returning required filenames, official URLs, sizes, and SHA-256 hashes without network access or execution.

Instructions

Verify the pinned Studio frontend JS/WASM in the private cache or a caller-selected source_dir. Returns required filenames, official URLs, sizes and SHA-256. No network, login, execution or directory creation.

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

Input Schema

NameRequiredDescriptionDefault
source_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is partly covered; the description nonetheless adds real value by enumerating exactly which side effects do not occur (network, login, execution, directory creation). There is a mild tension with openWorldHint=true that an agent may notice, and the description does not say how a failed verification is reported, which keeps this below a 5.

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 sentences, zero filler: what is verified, where it looks, what comes back, and what side effects are excluded. The scope statement is front-loaded and the return fields follow immediately.

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 one optional parameter, no output schema and read-only annotations, the description covers location, output fields, and side-effect boundaries well. The remaining gap is failure/mismatch semantics — an agent cannot tell whether a missing or hash-mismatched file raises an error or is reported in the result — which matters for a verification 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 0% for the single optional source_dir parameter, so the description must carry the meaning — and it does add that source_dir is a caller-selected alternative to the private cache, which is not derivable from the bare {"type":"string"} schema. It still omits path format expectations, relative vs absolute handling, and what the default is when the parameter is omitted.

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?

"Verify the pinned Studio frontend JS/WASM" names a specific verb and resource, and the scoping phrase "in the private cache or a caller-selected source_dir" explains exactly what is being checked. It is clearly a read/verify operation distinct from an installer, but the description never names ai_modeling_runtime_install as the counterpart, so the differentiation is inferred from the verb rather than stated.

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

Usage Guidelines3/5

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

The description implies the use case (checking pinned assets are present and intact before trusting or installing them) but never states an explicit when-to-use, when-not-to-use, or which sibling to call instead. The negative constraints ("no network, login, execution or directory creation") describe side-effect boundaries more than call-selection guidance.

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

Deploy Server

Other Tools