Skip to main content
Glama
Sign In

Syl Guardian

by io.sylai
OverviewDiscussionsAdmin

guardian_request_upload

Get a pre-signed URL for uploading a large CSV (more than ~200 rows).

Use this instead of pasting rows into guardian_review. Returns upload_url, dataset_id and a ready-to-run curl command: run it (replace data.csv with your file; gzip is accepted with Content-Encoding: gzip), then call guardian_review with dataset_id (and no csv/data). The URL is single-use and expires after 30 minutes; the dataset is only usable by the same API key, and is single-use too: it is deleted when guardian_review reads it (even if that review fails), so request a new upload to retry. This call does not consume review quota.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: URL is single-use and expires after 30 minutes, dataset is scoped to the same API key, is deleted when guardian_review reads it even if that review fails, and this call does not consume review quota. The gzip content-encoding detail adds further practical context.

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?

The key routing decision is front-loaded in the first two sentences, followed by the operational lifecycle details. Every sentence carries non-redundant information; there is no filler.

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?

Complete for a zero-parameter tool with no output schema: the description covers the returned fields (upload_url, dataset_id, curl command), URL expiry, dataset single-use lifecycle, API-key scoping, and quota behavior. An agent has everything needed to call it and use the result correctly.

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, so there is nothing for the description to disambiguate; baseline is 4. It does usefully clarify that dataset_id must later be passed to guardian_review without csv/data, which prevents a downstream argument mistake.

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 ('Get a pre-signed URL for uploading a large CSV') with an explicit size threshold, and names the sibling it replaces ('Use this instead of pasting rows into guardian_review'). An agent can distinguish it from guardian_review immediately.

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?

Gives the exact condition for use (>~200 rows), the alternative it replaces, and the full follow-up workflow: run the curl command, then call guardian_review with dataset_id and no csv/data. When and when-not are both covered.

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

All Syl Guardian 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