WEIR AI

Get my license

get_license

Read-onlyIdempotent

Get full detail of a license the connected account can access, by external_id. Use for the owner's own records; for the public catalog use get_public_license. Licenses the account can't access return NOT_FOUND_OR_NOT_PUBLIC. Needs license:read. [Needs a connected WEIR AI account; scope license:read]

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": {
      "external_id": "<external_id>"
    },
    "name": "get_license"
  }
}

Input Schema

Name	Required	Description	Default
`external_id`	Yes	Public external_id of the license.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare the operation read-only and idempotent, but the description adds important context beyond them: a connected WEIR AI account is required, the license:read scope is required, and inaccessible licenses return NOT_FOUND_OR_NOT_PUBLIC.

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?

The description is compact and front-loaded: the core action comes first, followed by the sibling alternative, access behavior, and permission requirements. Every sentence adds useful operational information.

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?

For a simple one-parameter read operation with no output schema, the description covers purpose, alternative selection, error behavior, and authentication requirements. Nothing material appears to be missing for correct invocation.

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%, and the single external_id parameter is already documented in the schema. The description reinforces that lookup is by external_id but adds no format or syntax details beyond the schema.

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: get full detail of a license by external_id. It explicitly distinguishes the accessible-account record from the public catalog record by naming get_public_license.

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

Usage Guidelines5/5

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

It gives explicit usage routing: use this for the owner's own records and use get_public_license for the public catalog. It also states access constraints and the NOT_FOUND_OR_NOT_PUBLIC behavior, so the agent knows when this tool is appropriate.

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

All WEIR AI tools Inspect

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

Need Help?