Skip to main content
Glama
Sign In

uCAD

by app.ucad
OverviewDiscussionsAdmin

uCAD script language

specs
Read-onlyIdempotent

Call this FIRST in every session, before writing any uCAD script, even if you have notes or a skill about uCAD from before: the language (a small Python: every function, its arguments and the objects it returns, with the rules), how this service works, the reference examples, what is new. The language is at spec version e597bdd3ef now; a copy with another version is out of date.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent, closed-world operation. The description adds valuable behavioral context by making the call mandatory before scripting and by warning about stale spec versions, though it does not describe response size or caching behavior.

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 description is front-loaded with the most important instruction, 'Call this FIRST,' and packs the content list efficiently into one sentence. It is dense but not wasteful, and every clause contributes to correct usage.

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 specification retrieval tool with no output schema, the description is complete enough. It explains what the tool contains, when it must be called, and how to detect an outdated copy.

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 has zero parameters, so there is no parameter semantics burden. The description appropriately focuses on what the tool returns rather than inventing parameter details.

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 provides the uCAD script language specification, service behavior, reference examples, and recent changes. It distinguishes itself from script-execution siblings by instructing the agent to call it before writing any uCAD script, though it does not explicitly name alternatives.

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?

It gives an explicit when-to-use rule: call this FIRST in every session before writing any uCAD script, even if prior notes or skills exist. It also provides a version-freshness condition, stating that copies with another version are out of date.

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

All uCAD toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources