Skip to main content
Glama
easor

easor

by Markku-hur

List organizations with credentials

list_configured_organizations
Read-only

Lists organizations with their own credentials in the server's .env, showing names and Easor business IDs when available, and indicates shared APIs that may cover other organizations by number.

Instructions

Lists the organizations that have credentials of their own in this server's .env (from the variable names only, never their values), with the organization's name and business id from Easor when available. sharedApis names the APIs (GL_FI, SALES_FI) that also have shared credentials: those can cover organizations not in the list, which then have to be entered by number.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real value on top: it reads variable names only and never their values, which is the key safety/privacy detail for an agent. It also discloses the fallback behavior for organizations not present in the list. It does not cover error behavior or ordering, so it is strong but not exhaustive.

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?

Two sentences, front-loaded with the core purpose and then the shared-credential caveat, with no filler wording. The second sentence is dense but each clause carries necessary information about sharedApis and the number-entry fallback.

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?

There is no output schema, so the description must carry the return contract, and it does name the returned fields (organization name, business id when available, sharedApis). Combined with the zero-parameter schema and the read-only annotations, this is close to complete; only ordering or error conditions are 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the 100% schema coverage baseline applies. The description instead spends its words on the shape of the result, which is the more useful information here.

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 plus a precise scope: organizations that have credentials of their own in this server's .env, with name and business id from Easor. It clearly separates that set from organizations covered by shared credentials, which makes the tool's role distinguishable from generic organization lookups. It stops short of naming a sibling such as get_organisation_info as the alternative.

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 definition explains the condition where organizations will not appear (they are only covered by shared credentials for GL_FI and SALES_FI) and what to do then (enter them by number). That is useful contextual guidance, but it never explicitly says when to call this versus a sibling tool, nor does it state prerequisites or exclusions directly.

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