infoFree 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.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | ||
| content | Yes | ||
| x-artifact-type | No | text |
Changes observed during successful MCP inspections.
Output schema / $defsRemoved value: -{
- "ExecutionMetadata": {
- "properties": {
- "agent_name": {
- "type": "string"
- },
- "context_id": {
- "type": "string"
- },
- "execution_id": {
- "type": [
- "string",
- "null"
- ]
- },
- "session_id": {
- "type": "string"
- },
- "skill_id": {
- "type": [
- "string",
- "null"
- ]
- },
- "skill_name": {
- "type": [
- "string",
- "null"
- ]
- },
- "task_id": {
- "type": [
- "string",
- "null"
- ]
- },
- "timestamp": {
- "type": "string"
- },
- "tool_name": {
- "type": [
- "string",
- "null"
- ]
- },
- "trace_id": {
- "type": "string"
- },
- "user_id": {
- "type": "string"
- }
- },
- "required": [
- "context_id",
- "trace_id",
- "session_id",
- "user_id",
- "agent_name",
- "timestamp"
- ],
- "type": "object"
- },
- "TextArtifact": {
- "properties": {
- "content": {
- "type": "string"
- },
- "title": {
- "type": [
- "string",
- "null"
- ]
- },
- "x-artifact-type": {
- "default": "text",
- "type": "string"
- }
- },
- "required": [
- "content"
- ],
- "type": "object"
- }
-}Output schema / properties / _metadataRemoved value: -{
- "$ref": "#/$defs/ExecutionMetadata"
-}Output schema / properties / artifactRemoved value: -{
- "$ref": "#/$defs/TextArtifact"
-}Output schema / properties / artifact_idRemoved value: -{
- "type": "string"
-}Output schema / properties / contentAdded value: +{
+ "type": "string"
+}Output schema / properties / mcp_execution_idRemoved value: -{
- "type": "string"
-}Output schema / properties / titleAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / x-artifact-typeAdded value: +{
+ "default": "text",
+ "type": "string"
+}Output schema / requiredPrevious value: -[
- "artifact_id",
- "mcp_execution_id",
- "artifact",
- "_metadata"
-]New value: +[
+ "content"
+]Output schema / titlePrevious value: -"ToolResponse"New value: +"TextArtifact"Input schema / additionalPropertiesAdded value: +trueDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, and the description adds valuable behavioral context: the tool is free, never returns a 402, and precedes paid operations. This goes beyond the annotation baseline without contradicting it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Every sentence earns its place: the tool's nature is front-loaded, followed by what it explains, cost safety, and the critical ordering instruction. The description is compact with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameter-free info tool with an output schema and annotations, the description covers purpose, pricing behavior, payment options, and when to call it. Nothing essential is missing for an agent to use this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters and the schema coverage is 100%, so no parameter documentation is needed. The description appropriately omits parameter details and instead focuses on usage context, matching the baseline for a no-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies this as a free usage guide for the server, with a specific verb ('explains') and resource ('usage guide'). It explicitly distinguishes itself from the paid report tools by stating it costs nothing and should be called first.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Call this first before any paid tool,' giving a direct usage instruction. It also clarifies what the tool covers—input requirements, pricing, and payment—so an agent knows exactly when to invoke it versus a paid sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.