Skip to main content
Glama

Caelara Shield

shield_proxy_fetch

Fetch an https URL through an SSRF-guarded proxy and return a JSON envelope with the scanned body (HTTP 200 envelope, upstream status inside) (0.025 USDC per call)

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

Input Schema

NameRequiredDescriptionDefault
urlNoTarget https URL (alternative to putting the URL in the path)
allowNoComma-separated hostnames or *.suffix patterns; when set the target must match
include_blockedNoReturn the body even when the content scan verdict is block (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 real work: it discloses the SSRF guard, the JSON envelope, that the HTTP 200 is an envelope with the real upstream status nested inside, and a per-call cost of 0.025 USDC. It also implies a content-scan/block verdict stage. Remaining gaps are redirect handling, payload size limits, and failure modes other than a block verdict.

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?

A single front-loaded sentence with no filler; the verb and guard mechanism come first, and the pricing and envelope caveats are packed into trailing parentheticals. Nothing is repeated or padded.

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?

For a three-parameter proxy-fetch tool with no output schema and no annotations, the description supplies enough: it explains the response shape (envelope, upstream status inside), the scan behavior, and the cost. An agent can call it and interpret the result without further context.

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?

Schema description coverage is 100%, so the three parameters are already documented in the schema. The description reinforces the content-scan verdict concept behind include_blocked and clarifies that the returned body is 'scanned', but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 and resource ('fetch an https URL') with the distinctive mechanism ('through an SSRF-guarded proxy'), which clearly separates it from shield_scan_prompt, shield_validate_output and shield_audit_token. It stops short of naming when a sibling would be preferred, but the operation itself is unambiguous.

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?

Usage is only implied: the SSRF framing suggests retrieving untrusted external content, and the per-call price hints at a metered operation. There is no explicit when-to-use or when-not-to-use statement, and no prerequisites (auth, quota, allowed URL forms) are described.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources