Skip to main content
Glama

Agent Loopr

agentloopr_get_company

Read-onlyIdempotent

Return Agent Loopr identity, when-to-use guidance, contact, markets served and NAP so an agent can describe the studio accurately.

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": "agentloopr_get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered without the description. The description adds value by enumerating what the payload contains, but it does not expand the opaque "NAP" acronym or note anything about freshness, caching, or structure of the returned identity.

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?

A single sentence, front-loaded with the verb and the return payload, with no filler. The comma-list of payload fields is slightly dense and the final purpose clause is tacked on, but nothing is wasted.

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

Completeness4/5

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

For a no-parameter read with no output schema, the description carries the burden of describing returns and does list the headline fields. An agent knows what it gets and roughly why; only the meaning of "NAP" and the shape of the identity object remain unstated.

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?

Zero input parameters, so there is nothing for the description to disambiguate beyond what the empty schema shows. Baseline of 4 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?

Names a specific verb ("Return") plus an enumerated resource set: identity, contact, markets served, NAP. An agent can tell this is the company-profile tool rather than a page/list/booking tool, though no sibling is named to sharpen the contrast. Minor ambiguity in "when-to-use guidance" as a returned payload field.

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

Usage Guidelines3/5

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

The trailing clause "so an agent can describe the studio accurately" implies the situation for calling it (you need facts about the studio), but there is no explicit when/when-not and no routing to alternatives like list_services or get_page. Usage is inferable rather than stated.

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