systemprompt.io reports

Usage guide

info

Read-only

Free usage guide for this server. Explains how the paid report tools work: exact input requirements, per-call pricing, and how to complete payment via x402 (USDC on Base) or Stripe checkout. Costs nothing and never returns a 402. Call this first before any paid tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`artifact`	Yes
`_metadata`	Yes
`artifact_id`	Yes
`mcp_execution_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 28, 2026
- addedInput schema / additionalProperties
```
Added value: +true
```
First observedJul 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=true), description adds key behaviors: free, never returns 402, and explains pricing/payment. No contradictions.

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, front-loaded with 'Free usage guide', every sentence adds value with no waste.

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?

Given no parameters and existence of output schema, description fully covers purpose, usage, and behavioral guarantees. Complete for this 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?

Input schema has zero parameters, so baseline is 4. Description adds no parameter info, but none needed.

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?

Description clearly states it's a free usage guide for paid report tools, explaining input requirements, pricing, and payment. It distinguishes itself from the sibling tool (eu_ai_act_compliance) by being the prerequisite guide.

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?

Explicitly instructs to call this first before any paid tool, and notes it costs nothing and never returns a 402. Provides clear when-to-use and context.

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

All systemprompt.io reports tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: eu_ai_act_compliance generates a paid compliance report, while info provides a free usage guide. There is no overlap or confusion.

Naming Consistency4/5

Both tools use snake_case, but 'info' is generic and not as descriptive as the lengthy 'eu_ai_act_compliance'. Consistency is acceptable given the small set.

Tool Count4/5

Two tools is slightly low but appropriate for a server focused on a single paid report. The info tool is essential for guiding payment, so the count feels reasonable.

Completeness5/5

The server fully covers its intended purpose: generating a compliance report and providing instructions. There are no obvious gaps for its scope.

Resources

Need Help?