Skip to main content
Glama

Get a paid service's full record

get_service_details
Read-onlyIdempotent

Full record for one listing id: request and response schemas, sample_query, observed 402 terms (network, payTo, scheme, x402 version), reputation detail, and paid_verification (our latest real USDC purchase, with its settlement tx where proven). Useful before paying: it shows the exact request shape and current reliability. Every timestamp has an _iso twin; on-chain counts describe the seller's wallet, usually shared by several listings, not this endpoint. Free, read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_service_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing id: the id field of a search result, e.g. f094faea-d9d.

Output Schema

NameRequiredDescriptionDefault
idYes
kindNo
nameYes
scoreNo
chainsNo
statusYes
categoryNo
transportNo
has_sampleNo
kind_notesNo
obs_pay_toNo
obs_schemeNo
payto_noteNo
descriptionNo
mpp_methodsNo
obs_networkNo
probe_countNo
endpoint_urlYes
price_amountYes
report_countNo
report_scoreNo
sample_queryNo
x402_versionNo
evidence_noteNo
evidence_tierNo
onchain_dailyNo
onchain_scopeNo
onchain_shapeNo
paid_verifiedNo
probes_failedNo
probes_passedNo
response_mimeNo
last_probed_atNo
onchain_walletNo
p50_latency_msNo
p95_latency_msNo
p99_latency_msNo
payto_sentinelNo
payto_unstableNo
price_currencyNo
request_schemaNo
distinct_payersNo
response_schemaNo
observed_networkNo
paid_verified_atNo
paid_verificationNo
payment_protocolsNo
status_changed_atNo
latest_purchase_atNo
verdict_age_secondsNo
paid_verified_at_isoNo
payto_distinct_recentNo
latest_purchase_age_daysNo
paid_verification_latestNo
latest_purchase_deliveredNo
onchain_unique_payers_30dNo
onchain_payto_shared_listingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / latest_purchase_age_days
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / latest_purchase_at
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / latest_purchase_delivered
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Listing id, as returned by find_paid_service."New value: +"Listing id: the id field of a search result, e.g. f094faea-d9d."
  3. Changed8 schema fields changed
    • removedOutput schema / properties / chains / description
      Removed value: -"Networks you can PAY on, as declared by the seller. Not the data or chains the service covers."
    • removedOutput schema / properties / mpp_methods / description
      Removed value: -"MPP methods as the endpoint names them (tempo, evm, stripe, ...); null when its 402 offers no MPP."
    • removedOutput schema / properties / onchain_payto_shared_listings / description
      Removed value: -"Active listings naming the same payTo address. Above 1, the on-chain figures are the wallet's, not this endpoint's."
    • removedOutput schema / properties / onchain_scope / description
      Removed value: -"What the on-chain figures describe, in words. Read before quoting them."
    • removedOutput schema / properties / onchain_wallet / description
      Removed value: -"On-chain activity of the seller's payment wallet (payTo), usually shared by many listings: scope, shared_by_listings, pay_to, tx_count_30d, unique_payers_30d, volume_usd_30d. Not this endpoint's own usage."
    • removedOutput schema / properties / p50_latency_ms / description
      Removed value: -"Median latency over the last 7 days (timeouts included); null under 5 probes."
    • removedOutput schema / properties / payment_protocols / description
      Removed value: -"Protocols the endpoint's own 402 offered on our unpaid probes: x402, mpp, or both. Paid verification covers x402 on Base only."
    • removedOutput schema / properties / probe_count / description
      Removed value: -"Every counted probe, passes AND failures. Passes are probes_passed."
  4. Changed2 schema fields changed
    • addedOutput schema / properties / mpp_methods
      Added value: +{
      +  "description": "MPP methods as the endpoint names them (tempo, evm, stripe, ...); null when its 402 offers no MPP.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / payment_protocols
      Added value: +{
      +  "description": "Protocols the endpoint's own 402 offered on our unpaid probes: x402, mpp, or both. Paid verification covers x402 on Base only.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. Changed2 schema fields changed
    • addedOutput schema / properties / onchain_wallet
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "On-chain activity of the seller's payment wallet (payTo), usually shared by many listings: scope, shared_by_listings, pay_to, tx_count_30d, unique_payers_30d, volume_usd_30d. Not this endpoint's own usage.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / p50_latency_ms / description
      Added value: +"Median latency over the last 7 days (timeouts included); null under 5 probes."
  6. Changed8 schema fields changed
    • addedOutput schema / properties / chains / description
      Added value: +"Networks you can PAY on, as declared by the seller. Not the data or chains the service covers."
    • addedOutput schema / properties / onchain_payto_shared_listings
      Added value: +{
      +  "description": "Active listings naming the same payTo address. Above 1, the on-chain figures are the wallet's, not this endpoint's.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / onchain_scope
      Added value: +{
      +  "description": "What the on-chain figures describe, in words. Read before quoting them.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / paid_verified_at
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / paid_verified_at_iso
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / probe_count / description
      Added value: +"Every counted probe, passes AND failures. Passes are probes_passed."
    • addedOutput schema / properties / probes_failed
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / probes_passed
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  7. Changed1 schema field changed
    • addedOutput schema / properties / paid_verification_latest
      Added value: +{
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  8. Changed1 schema field changed
    • addedOutput schema / properties / payto_sentinel
      Added value: +{
      +  "type": "boolean"
      +}
  9. Changed29 schema fields changed
    • addedOutput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / chains
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / distinct_payers
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / endpoint_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / evidence_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / evidence_tier
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / has_sample
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / kind
      Added value: +{
      +  "enum": [
      +    "api",
      +    "agent"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / last_probed_at
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / observed_network
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / onchain_unique_payers_30d
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / p50_latency_ms
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / p95_latency_ms
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / p99_latency_ms
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / paid_verified
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / price_amount
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / price_currency
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / probe_count
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / report_count
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / report_score
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / response_mime
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / score
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / status
      Added value: +{
      +  "enum": [
      +    "verified",
      +    "unverified",
      +    "failing"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / status_changed_at
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / verdict_age_seconds
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / x402_version
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  10. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "kind_notes": {
      +      "additionalProperties": true,
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "obs_network": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "obs_pay_to": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "obs_scheme": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "onchain_daily": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "onchain_shape": {
      +      "additionalProperties": true,
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "paid_verification": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "payto_distinct_recent": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "payto_note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "payto_unstable": {
      +      "type": "boolean"
      +    },
      +    "request_schema": {
      +      "additionalProperties": true,
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "response_schema": {
      +      "additionalProperties": true,
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "sample_query": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "transport": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "endpoint_url",
      +    "status",
      +    "price_amount"
      +  ],
      +  "type": "object"
      +}
  11. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so 'Free, read-only' is largely redundant. However the description adds genuinely non-obvious interpretation context: every timestamp has an _iso twin, and on-chain counts reflect the seller's shared wallet rather than this endpoint — real behavioral detail 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.

Conciseness5/5

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

Three dense sentences with zero filler: contents first, then the decision-driving use case, then the interpretive caveats. Front-loaded and every clause carries information.

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?

Output schema exists, annotations cover the safety profile, and the one parameter is fully documented. The description fills the remaining gap — how to read timestamps and wallet-level counts — so nothing needed for correct interpretation is missing.

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?

Single parameter with 100% schema description coverage, including an example id, so the schema does the work. The description only restates 'one listing id' and adds no format or sourcing detail beyond the schema — baseline 3.

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 resource and scope — 'Full record for one listing id' — then enumerates exactly what the record contains (request/response schemas, sample_query, 402 terms, reputation, paid_verification). An agent can distinguish this from find_paid_service or resolve_endpoint without opening a schema.

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?

'Useful before paying: it shows the exact request shape and current reliability' gives a clear selecting condition and timing for invocation. It does not name a sibling as the alternative or state when to avoid this tool, so it falls short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.