Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Inspect Public Source

inspectPublicSource
Destructive

Read a public GitHub repository or template and preview what it would deploy, with no token required.

Instructions

Read a public GitHub repository, or a template, and preview what it would deploy. Public: no token needed. Answers 429 when GitHub's rate limit, shared by every caller, runs out. Signed in, use inspectSource.

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

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.3/5.0
Behavior3/5

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

It adds genuinely useful behavior beyond the annotations: public access needs no token, and rate limiting is global and surfaces as 429. However, annotations declare readOnlyHint=false and destructiveHint=true, while the description frames the operation as "read ... and preview"; it never explains what side effects or state the preview creates, so the risk profile stays ambiguous. Not flagged as a contradiction because "preview" does not explicitly promise a side-effect-free call.

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?

Four short sentences, no filler, with the core purpose and the public/no-token constraint front-loaded before the rate-limit note and the sibling pointer. Every sentence carries information.

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?

For a tool with a nested oneOf request body and no output schema, the description does not indicate what "preview" actually returns (services, build config, warnings) or how large a response to expect. The routing, auth, and rate-limit facts are covered, but the return shape is left unstated.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the two payload modes (repoUrl vs template) map to public sources, and the token field is explicitly unnecessary here. That clarifies why an agent should not send a token to this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb+resource pair ("Read a public GitHub repository, or a template") and states the outcome ("preview what it would deploy"). It also names the sibling it is not (inspectSource), so an agent can route between the two without opening either schema.

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 selection rule: use this one for public sources with no token, and "Signed in, use inspectSource" for the authenticated path. Both the use case and the alternative are spelled out, leaving nothing to inference.

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