Skip to main content
Glama

Jid: the trust API for AI agents

Get a business file

get_business_file
Read-onlyIdempotent

The Jid file for one business. Default (compact): status with its flags, identifiers, verified websites, the top facts with source and verification date, counts and the latest changes. With detail "full": every current fact with its source, verification date, next check and confidence, owner statements (labelled self-reported), possible matches and the change history.

Input Schema

NameRequiredDescriptionDefault
idYesJid file id from search_business, e.g. gland-pharma-limited-j9nehi
detailNocompact (default): the verdict, status, identifiers and top facts with sources; full: every fact with its provenance

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
kindNo
nameYes
noteYesTerms of use for the facts
countsNo
statusYes
locationNo
full_fileNo
top_factsNo
facts_totalNo
identifiersNo
owner_statusNoclaimed | public_record
recent_changesNo
file_checked_atNo
identifiers_totalNo
websites_verifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default): the verdict, status, identifiers and top facts with sources; full: every fact with its provenance",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "counts": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "context_facts": {
      +          "type": "number"
      +        },
      +        "events": {
      +          "type": "number"
      +        },
      +        "facts": {
      +          "type": "number"
      +        },
      +        "possible_matches": {
      +          "type": "number"
      +        },
      +        "self_reported": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "facts",
      +        "context_facts",
      +        "self_reported",
      +        "possible_matches",
      +        "events"
      +      ],
      +      "type": "object"
      +    },
      +    "facts_total": {
      +      "type": "number"
      +    },
      +    "file_checked_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "full_file": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "api": {
      +          "type": "string"
      +        },
      +        "detail_full": {
      +          "type": "string"
      +        },
      +        "page": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "page",
      +        "api"
      +      ],
      +      "type": "object"
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "identifiers": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "type": {
      +            "type": "string"
      +          },
      +          "value": {}
      +        },
      +        "required": [
      +          "type",
      +          "value"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "identifiers_total": {
      +      "type": "number"
      +    },
      +    "kind": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "location": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "city": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "country": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "region": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "country",
      +        "region",
      +        "city"
      +      ],
      +      "type": "object"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "description": "Terms of use for the facts",
      +      "type": "string"
      +    },
      +    "owner_status": {
      +      "description": "claimed | public_record",
      +      "type": "string"
      +    },
      +    "recent_changes": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "occurred_at": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "source": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "summary": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "occurred_at",
      +          "summary",
      +          "source"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "flags": {
      +          "description": "Compact: \"tone: label\" strings; full: objects",
      +          "items": {},
      +          "type": "array"
      +        },
      +        "rules": {
      +          "type": "string"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "summary": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "status"
      +      ],
      +      "type": "object"
      +    },
      +    "top_facts": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "label": {
      +            "type": "string"
      +          },
      +          "predicate": {
      +            "type": "string"
      +          },
      +          "source": {
      +            "type": "string"
      +          },
      +          "source_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "value": {},
      +          "value_truncated": {
      +            "const": true,
      +            "type": "boolean"
      +          },
      +          "verified_at": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "predicate",
      +          "value"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "websites_verified": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "url",
      +    "status",
      +    "note"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the compact vs full content profile and flagging that owner statements are self-reported, a trust-relevant trait not captured anywhere else.

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?

Two sentences, front-loaded with the default mode before the expanded mode, and every clause enumerates actual returned fields rather than padding. It is dense but no sentence is wasted.

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?

An output schema exists, so return-value documentation is not strictly required, and annotations cover the safety profile; the description nonetheless rounds out the picture with detail-mode contents and provenance caveats. The only untouched area is sibling-relative routing guidance.

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?

Schema coverage is 100%, so the baseline is 3, but the description meaningfully enriches the 'detail' enum by enumerating the concrete fields returned in each mode (e.g. 'next check and confidence', 'change history') beyond the schema's one-line gloss. The id parameter's origin is also reinforced.

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?

States a specific resource ('the Jid file for one business') and enumerates what the payload contains at each detail level, so the agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings like search_business or verify_business, which keeps it short of a 5.

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?

Usage is only implied: the id parameter description points at search_business as the source of the id, which hints at the workflow (search then fetch), but there is no explicit statement of when to use this tool versus verify_business or screen. Adequate but with a clear routing gap.

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.

Resources