Skip to main content
Glama

Organization identity links

bpj_organization_profile_links
Read-onlyIdempotent

Validate and deduplicate identity profile URLs for an Organization and its website.

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": {
      "name": "<name>",
      "url": "<url>",
      "profiles": "<profiles>"
    },
    "name": "bpj_organization_profile_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
profilesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond the verb: it does not say whether validation failures are reported per URL, what the deduplicated output looks like (there is no output schema), or how malformed lines are handled.

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

Conciseness3/5

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

A single front-loaded sentence with no filler or redundancy, which is structurally sound. However, the brevity is achieved by omission rather than compression, leaving the tool under-specified for its three required inputs.

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

Completeness2/5

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

For a tool with three required parameters, no documented schema coverage, and no output schema, one sentence is far too thin. An agent cannot determine input format (newline-delimited profiles, URL length limits) or what it will receive back, which the description would need to supply given the missing output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description accounts for only one of the three parameters loosely ("identity profile URLs" ~ profiles); it says nothing about the required name and url parameters. It also omits the one format detail an agent would most need, that profiles is one URL per line — that clue exists only in the schema title, not in the description.

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?

The description names a specific verb pair ("Validate and deduplicate") and a specific resource ("identity profile URLs for an Organization and its website"), which the bare name/title ("Organization identity links") does not. It is distinguishable from siblings like bpj_extract_web_links because the emphasis is on validation and dedup rather than extraction, though it never says what the validated result is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus alternatives such as bpj_extract_web_links or the other profile tools, and no prerequisites (e.g., that an Organization name and its page URL must be supplied alongside the profile lines). The only implicit cue is that the input is a block of profile URLs to be checked.

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.