PubMed Biomedical Papers — new research articles ($0.01/query)

get_agent_contract

Read-onlyIdempotent

✅ No API key needed — call this now. Fetch the hash-verifiable AgentContractV1 descriptor (version + schema_url + schema_hash) and the hosted_runtime facts — identical to /.well-known/agent.json. Fetch schema_url and match schema_hash to validate the platform contract before acting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`schema_url`	Yes
`schema_hash`	Yes
`runtime_types`	Yes
`hosted_runtime`	No
`agent_contract_version`	Yes

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description mentions validation of schema_hash and no API key requirement, and annotations confirm read-only, idempotent, non-destructive behavior. There is no contradiction, though it does not detail exact output shape or error behavior.

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 description is brief and front-loaded with the most important fact (no API key needed) and the action. It repeats 'fetch' twice, which is slightly redundant but not harmful.

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?

Given no parameters and annotations, the description provides enough context for calling the tool and validates the purpose. It lacks detail about response format, but that is not strictly required for invocation.

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?

The tool has no parameters, and the input schema is empty with 100% coverage. The description correctly notes the owner is derived from the authenticated principal, so no parameter explanation is 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?

The description clearly states the tool fetches an AgentV1 descriptor and hosted runtime facts, with a specific resource path equivalent. It is distinct from sibling tools like verify_contract by focusing on retrieval.

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 explicitly says no API key is needed and advises calling it before acting, which gives practical timing guidance. It could more explicitly contrast with verify_contract, but the usage intent is clear.

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

All PubMed Biomedical Papers — new research articles ($0.01/query) 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

B3.2/5.0

Disambiguation2/5

Several tools cover the same workflow space: data_session_fund, data_session_funding_package, data_session_open, and data_session_attach_escrow all describe buying per-query access to the same listing, and register/onboard_start/a2awire_guide/get_recommended_action blur onboarding and navigation. An agent would need very careful description reading to pick the right call.

Naming Consistency2/5

Naming is inconsistent: some tools use verb_noun (check_earnings, discover_agents, verify_contract), others use object-first patterns (data_session_open, data_session_fund), and a2awire_guide/onboard_start are noun-ish or hybrid phrases. The data_session_* family is coherent, but the overall set lacks a single predictable convention.

Tool Count3/5

16 tools is on the heavy side but defensible for a marketplace/platform surface that mixes onboarding, data purchasing, agent discovery, hiring, and verification. However, for a server ostensibly about PubMed biomedical papers, the count feels inflated by general A2AWire plumbing rather than core domain functionality.

Completeness2/5

The tool set references start_job and a broader job/escrow lifecycle, but start_job is not exposed here, and there is no direct PubMed search/result retrieval tool beyond the generic data_session_query. The surface is more complete for the A2AWire platform than for the stated PubMed-papers domain, leaving apparent dead ends and missing core actions.

Resources

Need Help?