WEIR AI

Get one public license

get_public_license

Read-onlyIdempotent

Retrieve the public status, license category, available terms information, and terms link for a specific public WEIR license ID (e.g. WRT2TVR2A). Returns found:false with code NOT_FOUND_OR_NOT_PUBLIC when the ID is private or doesn't exist; that never reveals whether a private license exists and is never permission. Next step: share terms_url so the person can review the terms on WEIR AI; any licensing decision is made by the person there. [Public, no account needed]

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_public_license"
  }
}

Input Schema

Name	Required	Description	Default
`external_id`	Yes	Public external_id from search_catalog (e.g. WRT3E0FAY).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior beyond them: the found:false plus NOT_FOUND_OR_NOT_PUBLIC response shape, the privacy guarantee that a miss never reveals whether a private license exists, and the caution that the result 'is never permission'. It also discloses the auth posture ('Public, no account needed').

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?

The return fields are front-loaded, followed by the failure mode, then the next step, then an auth tag — a logical order with no filler. The middle clauses around the NOT_FOUND semantics are dense but each carries a distinct safety point, so only minor tightening is possible.

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 one-parameter read tool with no output schema, the description covers what is returned (including terms_url), the failure case and its error code, the privacy implication, and the intended follow-up action. Nothing an agent needs in order to call and interpret it is missing.

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 coverage is 100% and the single external_id parameter is already documented in the schema as coming from search_catalog. The description restates the example ID format but adds no new syntax or validation meaning, so the baseline 3 applies.

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 (retrieve) and resource (public WEIR license by external ID) and enumerates exactly what comes back: public status, license category, available terms, and terms_url. The 'public' qualifier plus the example ID format separates it from the private-license sibling, though it never names get_license as the alternative for non-public records.

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 a concrete workflow ('Next step: share terms_url so the person can review the terms on WEIR AI') and states that licensing decisions are made elsewhere, which tells the agent where its job ends. It lacks an explicit 'use get_license instead when X' routing statement against the sibling tools.

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?