Skip to main content
Glama
Sign In

The Comp Desk Builder

by com.thecompdesk
OverviewDiscussionsAdmin

pull_skill_scaffold

Return a valid, self-sufficient SKILL.md scaffold (autonomy: standalone + browser/local-files/user-input data sources + a no-backend fallback section) to start a new skill.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does add real content about the returned scaffold's composition (standalone autonomy, browser/local-file/user-input data sources, no-backend fallback), which tells the agent what it will get, but it omits whether anything is written or persisted and what format the result takes.

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?

A single front-loaded sentence that states the deliverable first and qualifies it afterward. The parenthetical is dense with unexpanded jargon, but no sentence is wasted.

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

Completeness3/5

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

With no output schema and no annotations, the description needs to carry the return-value explanation, and it only partially does — it names the scaffold's sections but not its format, length, or customizability. Adequate to invoke, thin for predicting what comes back.

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 zero parameters and the schema is fully described, so there is no parameter meaning for the description to add. Baseline 4 applies for a no-parameter tool.

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?

States a specific verb (return) and a specific resource (a SKILL.md scaffold) plus its intended use ('to start a new skill'). It is clear what the tool produces, though it never names or distinguishes itself from the sibling create_skill, which an agent would have to disambiguate on its own.

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 trailing clause 'to start a new skill' implies the usage context (before authoring a new skill), but there is no explicit when-to-use versus when-not guidance and no mention of alternatives such as create_skill. Usage is inferable rather than stated.

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

All The Comp Desk Builder 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