Synthex Forge — x402 Paid Agent Services

Search Social Signals

search_social_signals

Read-onlyIdempotent

Multi-channel social-signal search. use it rather than search_forensics_evidence for social signals, not forensics evidence; an object with 11 fields including channels, data_source. $0.02 USDC.

Input Schema

Name	Required	Description
`q`	No	The q this operation operates on. See the schema for its type and whether it is required.
`limit`	No	Maximum number of items to return.
`channels`	No	The channels this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`error`	No	The machine-readable error code, when the operation failed.
`limit`	No	The `limit` field of the response.
`query`	No	The `query` field of the response.
`reason`	No	Why the verdict was reached.
`status`	No	The status of the operation.
`partial`	No	The `partial` field of the response.
`results`	No	The results the operation produced.
`channels`	No	The `channels` field of the response.
`fetched_at`	No	The `fetched_at` field of the response.
`data_source`	No	The `data_source` field of the response.
`results_count`	No	The `results_count` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 31, 2026

addedOutput schema / properties / channels

Added value: +{
+  "description": "The `channels` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / data_source

Added value: +{
+  "description": "The `data_source` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "description": "The machine-readable error code, when the operation failed.",
+  "type": "string"
+}

addedOutput schema / properties / fetched_at

Added value: +{
+  "description": "The `fetched_at` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / limit

Added value: +{
+  "description": "The `limit` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / partial

Added value: +{
+  "description": "The `partial` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / query

Added value: +{
+  "description": "The `query` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / results

Added value: +{
+  "description": "The results the operation produced.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results_count

Added value: +{
+  "description": "The `results_count` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description does not need to restate them. It adds non-obvious operational context instead: the call costs $0.02 USDC and returns an object with 11 fields. It still says nothing about result volume, pagination, or how channels affect behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the routing instruction comes early, but the middle clause ("an object with 11 fields including channels, data_source") is a dangling fragment with no verb and no clear referent, forcing the reader to guess whether it describes output or input. The price is tacked on at the end rather than integrated.

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?

For a three-parameter read-only search with a full output schema, the description supplies the essentials an agent needs: what it searches, which sibling to prefer, and the cost. The garbled return-value fragment is redundant given the output schema but not harmful; missing pagination and `q` syntax guidance are the remaining gaps.

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 baseline is 3, but the schema text is boilerplate ("The q this operation operates on..."), which adds little real meaning. The description could have compensated by explaining what `q` accepts or how `channels` and `limit` behave, but it does not mention any parameter at all.

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 opening sentence names a specific verb and resource ("Multi-channel social-signal search") and immediately contrasts it with the sibling `search_forensics_evidence`, so an agent can route correctly without opening either schema. The additional note about channels/data_source and the per-call price further pins down what this tool is for.

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 names the exact alternative and the condition that selects it: use this for social signals, not forensics evidence. That is a genuine routing instruction rather than an implied one. It does not cover any other sibling or state prerequisites, so it falls short of a full when/when-not matrix.

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

All Synthex Forge — x402 Paid Agent Services tools Inspect

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.