Skip to main content
Glama

Registry Pages

Search Norwegian companies by name

search_norwegian_companies
Read-only

Find Norwegian units by name. Returns at most 10 matches with organisation number, municipality, status and page URL. Use get_norwegian_company for details.

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": {
      "query": "<query>"
    },
    "name": "search_norwegian_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany name, for example "equinor"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description still adds real behavioral value by disclosing the result cap ('at most 10 matches') and enumerating returned fields (organisation number, municipality, status, page URL), which tells the agent results may be truncated and no pagination exists. Matching semantics (substring vs prefix vs fuzzy) remain undisclosed.

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?

Three short sentences with zero filler: purpose, result shape, and the escalation path, in that order. The cap and return fields are front-loaded where an agent will see them before invoking.

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 lookup with no output schema, the description covers purpose, result cardinality, returned fields, and the follow-up tool. Combined with annotations that cover read-only and closed-world behavior, nothing material is 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 query parameter already carries an example ('equinor'). The description only restates that matching is by name, adding no syntax, formatting, or normalization guidance beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (Find) and resource (Norwegian units/companies) with the search dimension (by name) made explicit. The phrase 'Norwegian units' plus the pointer to get_norwegian_company cleanly separates it from the French/UK sibling searches and from the detail-getter.

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?

Explicitly routes the agent to get_norwegian_company when details are needed, which is the key alternative decision for this family of tools. It stops short of stating when-not to use it (e.g. that it only covers Norwegian entities and will not match foreign names), so it is clear but not fully exhaustive.

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