Skip to main content
Glama

Get provider info

get_provider_info
Read-onlyIdempotent

Get profile and active listings for an enrichment activity provider (organization). Pass organization_id from search_activities results, or provider_name to look up by name (optionally narrowed by city/state).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city narrowing for provider_name lookup
stateNoOptional two-letter US state narrowing for provider_name lookup
provider_nameNoProvider name to resolve when organization_id is unavailable
organization_idNoProvider organization ID from search_activities results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / organization_id / maximum
      Added value: +2147483647
  2. Changed5 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "Optional city narrowing for provider_name lookup",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / organization_id / description
      Previous value: -"Provider organization ID"New value: +"Provider organization ID from search_activities results"
    • addedInput schema / properties / provider_name
      Added value: +{
      +  "description": "Provider name to resolve when organization_id is unavailable",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Optional two-letter US state narrowing for provider_name lookup",
      +  "maxLength": 2,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "organization_id"
      -]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds that only 'active' listings are returned, but says nothing about not-found behavior, ambiguous name matches, or how many results to expect.

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?

Two sentences, zero waste, with the primary key path front-loaded and the fallback path clearly subordinate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All four parameters are optional, and the description never says what happens when neither organization_id nor provider_name is supplied, nor how multiple name matches are resolved. With no output schema, a sentence on the returned shape or ambiguity handling would close the remaining gaps.

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 adds real value: precedence between organization_id and provider_name, and the fact that city/state only narrow the name-based path rather than the ID path — a constraint the schema descriptions state only partially.

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 verb and resource ('Get profile and active listings for an enrichment activity provider') and clarifies that a provider is an organization, which removes domain ambiguity. It references search_activities as the source of IDs, which helps separate it from get_activity_details, though that sibling is never named directly.

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?

Gives an explicit lookup strategy: prefer organization_id from search_activities results, otherwise fall back to provider_name, optionally narrowed by city/state. It stops short of stating when not to use this tool (e.g., to get activity-level detail, use get_activity_details).

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