Skip to main content
Glama
Sign In

McpStamp Contract Clauses

by io.github.theluckystrike
OverviewDiscussionsAdmin

Export clauses

clause_export
Read-onlyIdempotent

Call this tool to write the whole library to one file and return the path, format and count. It is written in contract order, so it re-imports the same way. markdown is free; json is Pro.

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": {
      "path": "<path>",
      "format": "<format>"
    },
    "name": "clause_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDestination file path. The clauses are written in assembly order, categories first
formatYesjson (a Pro feature) or markdown (works in the free tier)
overwriteNoReplace the destination if a file is already there. Without it an existing file is never touched

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A3.6/5.0
Behavior1/5

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

The description states the tool will 'write the whole library to one file,' which is a side-effecting operation, while the annotation declares readOnlyHint=true. This directly contradicts the annotations, so the behavioral transparency score is the minimum per the rubric.

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 sentences, each adding useful information: what the tool does, the ordering/round-trip behavior, and the format restriction. The core action is front-loaded and there is no filler.

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 no output schema, the description usefully discloses the return tuple (path, format, count) and the re-import behavior. It is mostly complete for a simple export tool, but the contradictory readOnlyHint creates ambiguity about side effects.

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?

The input schema already documents all three parameters with 100% coverage, so the baseline applies. The description repeats the markdown/json pricing distinction already present in the schema and adds no meaningful parameter semantics beyond it.

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 uses a specific verb phrase, 'write the whole library to one file and return the path, format and count,' which clearly identifies the operation. It also distinguishes itself from the sibling clause_import by noting the export re-imports the same way.

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?

It explicitly opens with 'Call this tool to write the whole library to one file,' which gives clear guidance on the intended use. It does not explicitly list exclusions or alternative tools, but the purpose is well-scoped enough that an agent can infer when it applies.

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

All McpStamp Contract Clauses 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