Skip to main content
Glama

PXL8 verified fight records

by io.pxl8
OverviewDiscussionsAdmin

Fetch one record

fetch
Read-onlyIdempotent

Read one record by the id search returned (person:, organization:, fighter:, parcel:/, provider:, au_company:, chrb_ruling:, cpsc_recall:, eu_sanction:, eu_tender_notice:, fdic_institution:, legal_entity:, jp_corporation:, khrc_ruling:, vehicle_manufacturer:, exclusion:, fda_device_recall:, sg_entity:, company:, uk_contracts_finder_notice:, uk_tender_notice:, uk_sanction:, significant_control:, facility:, motor_carrier:, contract_notice: or restricted_party:). Answers { id, title, text, url, metadata } as one JSON document; metadata carries kind, recordStatus, citeAs and lastReviewed. The text presents facts in three separate grades, each its own list; a fact stated by the subject is the subject's own statement; a disputed fact remains present, marked Disputed. The url and the citeAs line in metadata identify the page for attribution. Each result carries its url and the citeAs attribution line in metadata; a disputed fact remains in the answer, marked with the word Disputed. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAn id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, jp_corporation:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, jp_corporation:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"
  4. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, company:<subject_key>, uk_sanction:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"
  5. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, company:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, company:<subject_key>, uk_sanction:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"
  6. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, company:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, company:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"
  7. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, company:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"
  8. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key> or fda_device_recall:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, motor_carrier:<subject_key> or restricted_party:<subject_key>"
  9. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, vehicle_manufacturer:<subject_key> or fda_device_recall:<subject_key>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key> or fda_device_recall:<subject_key>"
  10. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle>, fighter:<slug> or parcel:<jurisdiction>/<apn>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, cpsc_recall:<subject_key>, fdic_institution:<subject_key>, vehicle_manufacturer:<subject_key> or fda_device_recall:<subject_key>"
  11. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: person:<handle>, organization:<handle> or fighter:<slug>"New value: +"An id from search: person:<handle>, organization:<handle>, fighter:<slug> or parcel:<jurisdiction>/<apn>"
  12. Changed1 schema field changed
    • changedInput schema / properties / id / maxLength
      Previous value: -173New value: +257
  13. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine behavioral context beyond them: rate limits per client and in total, plus a keyed partner tier with higher limits. It also discloses the response shape and the disputed-fact handling, though the fact-grade explanation is repetitive and slightly muddled.

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

Conciseness2/5

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

The long id-prefix enumeration is copy-pasted from the schema, front-loading bloat before any behavioral information. The url/citeAs attribution and the Disputed-fact rule are each stated twice, which is pure redundancy in an already lengthy description.

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 carries the return contract and does so: { id, title, text, url, metadata } with metadata fields (kind, recordStatus, citeAs, lastReviewed). An agent has enough to call it, though error/not-found behavior for an unknown id is unstated.

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, and schema description coverage is 100%, so the schema already documents the id fully. The description reproduces the same prefix list verbatim rather than adding new meaning (no examples of real ids, no resolution/failure behavior), so it stays at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb+resource: 'Read one record by the id search returned,' and it explains the id format comprehensively. It implicitly routes from search but does not explicitly distinguish itself from overlapping siblings like get_subject or get_fighter_record, which appear to cover id kinds also listed here.

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?

'By the id search returned' implies the retrieve-after-search workflow, giving usable but implicit guidance. There is no explicit when-not-to-use or naming of alternative siblings, and the partner-access note describes an access tier rather than a usage condition.

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

All PXL8 verified fight records 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