Skip to main content
Glama
Sign In

SYNTHORA x402 Intelligence Mesh

by com.hergertsynthora
OverviewDiscussionsAdmin

doaj_article_search

Read-onlyIdempotent

Searches the Directory of Open Access Journals article index, returning titles, authors, DOIs, journal, ISSNs, abstracts and open-access full-text links as JSON. A keyless endpoint for autonomous research agents and agent-to-agent workflows sourcing legally free, peer-reviewed open-access literature. First 3 calls FREE per wallet — send header X-WALLET: 0x. No charge on upstream failure. [x402: 0.005 USDC per call on Base]

Input Schema

NameRequiredDescriptionDefault
queryYesquery

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "pageSize": 2,
+    "query": "machine learning"
+  }
+]
    • removedInput schema / properties / input
      Removed value: -{
-  "description": "product parameters (JSON or text). Example: {\"query\": \"machine learning\", \"pageSize\": 2}",
-  "type": "string"
-}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "query",
+  "examples": [
+    "machine learning"
+  ],
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "query"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"input\": \"{\\\"query\\\": \\\"machine learning\\\", \\\"pageSize\\\": 2}\"}"New value: +"product parameters (JSON or text). Example: {\"query\": \"machine learning\", \"pageSize\": 2}"
  3. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"query\": \"machine learning\", \"pageSize\": 2}"New value: +"product parameters (JSON or text). Example: {\"input\": \"{\\\"query\\\": \\\"machine learning\\\", \\\"pageSize\\\": 2}\"}"
  4. Added
  5. Removed
  6. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover the safety profile (read-only, idempotent, open-world, non-destructive); the description goes well beyond that by disclosing the payment model (x402 0.005 USDC on Base), a free tier (first 3 calls per wallet), the required X-WALLET header with format, and the no-charge-on-failure guarantee. This is exactly the kind of auth/cost behavior an agent cannot infer from annotations.

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

Conciseness4/5

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

The core capability is front-loaded in the first sentence, followed by audience framing and then the critical payment details. Some phrasing ('agent-to-agent workflows', 'legally free') is promotional, but every clause carries usable information.

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?

With no output schema, the description compensates by listing the return fields, and it fully covers the cost/auth mechanics needed to invoke the endpoint successfully. The only omission is query-syntax guidance, which is minor for a single free-text parameter.

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?

Only one parameter (query) and schema coverage is 100%, so the baseline is 3. The description adds no query syntax guidance (boolean operators, field targeting) that would help a search agent construct a valid query.

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 ('Searches the Directory of Open Access Journals article index') and enumerates the returned fields (titles, authors, DOIs, journal, ISSNs, abstracts, full-text links). No sibling tool overlaps this domain, so it is trivially distinguishable.

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?

The description frames the intended context ('autonomous research agents', 'legally free, peer-reviewed open-access literature') which implies when to reach for it, but never states when NOT to use it or names an alternative tool for adjacent needs. Usage is implied rather than explicit.

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

All SYNTHORA x402 Intelligence Mesh 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