Revid

Describe edit tools

describe_edit_tools

Read-only

List the tools edit_project accepts, each with one line and whether it costs credits. Name some in tools for their full description and JSON schema.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pid": "<pid>"
    },
    "name": "describe_edit_tools"
  }
}

Input Schema

Name	Required	Description	Default
`pid`	Yes	Revid project id.
`tools`	No	Tool names to describe in full.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`method`	Yes
`status`	Yes
`endpoint`	Yes
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered. The description adds genuinely new behavioral context: results are one line each, include a credit-cost flag, and can be expanded to full descriptions plus JSON schema on request.

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?

Two sentences, front-loaded with what the call returns, second sentence covering the optional expansion. No filler, no restatement of the tool name or annotations.

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 and annotations covering the safety profile, the description only needs to convey scope and the credit signal, both of which it does. It omits any note on the size or shape of the unfiltered listing, which is the one remaining ambiguity for a discovery tool.

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; the description earns a bump by clarifying what `tools` actually buys the caller (full description and JSON schema, not just a longer label). The `pid` requirement is left entirely to the schema, but that is acceptable given full coverage.

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?

States a specific verb and resource ('List the tools edit_project accepts') and scopes the output ('one line ... whether it costs credits'). Naming edit_project ties it directly to a sibling, so an agent can tell this is a discovery companion to that tool rather than a duplicate of any other sibling.

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

Usage Guidelines4/5

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

Implicitly positions itself as the pre-flight lookup for edit_project operations and explains the two usage modes (default one-line listing vs. naming tools in `tools` for full detail). It does not state exclusions or when not to bother calling it, so it falls short of full when/when-not guidance.

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

All Revid tools Inspect

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

Need Help?