Skip to main content
Glama
easor

easor

by Markku-hur

Get organisation info

get_organisation_info
Read-only

Retrieve organization details such as address, business ID, VAT period, and invoicing info by organization number to support accounting and reporting workflows.

Instructions

Returns organisation info (address, business id, VAT id/period/obligations, invoicing details, ...) from Easor's Organization API.

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": {
      "organizationNumber": "<organizationNumber>"
    },
    "name": "get_organisation_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationNumberYesEasor organization/customer number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful context by naming the backing system (Easor's Organization API) and by sketching the returned content, which compensates slightly for the absent output schema. It says nothing about behaviour when the organization number is unknown, about permissions, or about response shape beyond the field list.

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?

One sentence, front-loaded with the verb and resource, with the returned fields listed after. The trailing "..." signals an open-ended field list, which is mildly imprecise but keeps this compact and free of filler.

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 single-parameter read-only getter with 100% schema coverage and no output schema, the description does the main extra job: outlining what comes back (address, business id, VAT details, invoicing details). The remaining gap is failure/edge-case behaviour and any guidance on obtaining a valid organization number, which is minor for a tool of this complexity.

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?

The single parameter has full schema coverage ("Easor organization/customer number"), so semantics are already documented in the schema. The description adds no syntax, format, or validation meaning beyond what is there — the schema even permits negative integers without explanation, and the description does not clarify the accepted range.

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 gives a specific verb and resource ("Returns organisation info") and enumerates concrete content: address, business id, VAT id/period/obligations, invoicing details. That is far more informative than the title alone and lets an agent tell it apart from the accounting-period, dimension, ledger and report-building siblings, none of which cover organisation master data. It stops short of 5 only because it never states its relationship to any sibling explicitly.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to an alternative or prerequisite tool such as list_configured_organizations for discovering the organization number. An agent must infer from the name and description alone that this is the org-master-data getter.

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