Skip to main content
Glama

Get Business Credentials

get_credentials
Read-onlyIdempotent

Returns the business's self-reported licenses, insurance, bonding, and certifications. Use this for trust-sensitive verticals (contractors, healthcare, legal, locksmiths) when a user asks 'are they licensed?' or 'are they insured?'. The response carries explicit 'self-reported' framing so agents don't upgrade tenant claims to verified facts.

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug identifier

Output Schema

NameRequiredDescriptionDefault
slugYes
bondedYes
insuredYes
summaryYes
licensesYes
certificationsYes
has_credentialsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / bonded / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / bonded / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / insured / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / insured / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / slug / description
      Previous value: -"business slug"New value: +"Business slug identifier"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "bonded": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "certifications": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "has_credentials": {
      +      "type": "boolean"
      +    },
      +    "insured": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "licenses": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "expires_at": {
      +            "type": "string"
      +          },
      +          "jurisdiction": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "number": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "slug",
      +    "has_credentials",
      +    "licenses",
      +    "insured",
      +    "bonded",
      +    "certifications",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / slug / description
      Previous value: -"Business slug identifier"New value: +"business slug"
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "bonded": {
      -      "anyOf": [
      -        {
      -          "type": "boolean"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "certifications": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "has_credentials": {
      -      "type": "boolean"
      -    },
      -    "insured": {
      -      "anyOf": [
      -        {
      -          "type": "boolean"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "licenses": {
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "expires_at": {
      -            "type": "string"
      -          },
      -          "jurisdiction": {
      -            "type": "string"
      -          },
      -          "name": {
      -            "type": "string"
      -          },
      -          "number": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "name"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "slug": {
      -      "type": "string"
      -    },
      -    "summary": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "slug",
      -    "has_credentials",
      -    "licenses",
      -    "insured",
      -    "bonded",
      -    "certifications",
      -    "summary"
      -  ],
      -  "type": "object"
      -}New value: +null
  4. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / slug / description
      Previous value: -"business slug"New value: +"Business slug identifier"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "bonded": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "certifications": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "has_credentials": {
      +      "type": "boolean"
      +    },
      +    "insured": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "licenses": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "expires_at": {
      +            "type": "string"
      +          },
      +          "jurisdiction": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "number": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "slug",
      +    "has_credentials",
      +    "licenses",
      +    "insured",
      +    "bonded",
      +    "certifications",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile: read-only, idempotent, non-destructive, and closed-world. The description adds important behavioral context beyond that by emphasizing the 'self-reported' framing so agents do not treat tenant claims as verified facts. It stops short of describing freshness, pagination, or coverage limits, but the core caveat is well disclosed.

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 tightly written sentences with no waste. The purpose, usage context, and self-reported caveat are front-loaded. Each sentence earns its place.

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?

The tool has an output schema, rich annotations, and a simple single-parameter schema. The description supplies the crucial self-reported caveat and trust-sensitive usage context, so an agent has everything needed to call it correctly and interpret its claims responsibly.

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?

Schema description coverage is 100%, so the single 'slug' parameter is already documented in the schema. The description adds no additional parameter-level meaning, which is acceptable given the schema's completeness. Baseline 3 applies.

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 states a specific verb and resource: it returns the business's self-reported licenses, insurance, bonding, and certifications. That scope clearly distinguishes it from the booking, payment, and quote siblings. An agent can identify the tool's purpose without opening the 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?

It gives clear usage context: trust-sensitive verticals such as contractors, healthcare, legal, and locksmiths, and user questions like 'are they licensed?' or 'are they insured?'. It does not explicitly state when not to use the tool or name an alternative, so it falls short of a 5.

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