Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Stock Locations & Areas

bexio_stock
Read-onlyIdempotent

List or search stock locations and areas with filters on name or id, supporting pagination and ordering.

Instructions

Read stock locations and stock areas (both are simple id/name records; items reference them via stock_id and stock_place_id). All actions require the stock_edit scope. Actions: "list_locations" (all stock locations, optional limit/offset/order_by; order by "id" or "name"), "search_locations" (search_criteria required; searchable fields: name, id), "list_areas" (all stock areas, optional limit/offset/order_by; order by "id" or "name"), "search_areas" (search_criteria required; searchable fields: name, id). Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive; description adds that actions require 'stock_edit' scope and details each action's behavior, including searchable fields and ordering options.

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?

Two sentences, front-loaded with purpose, no wasted words. Actions and parameters described compactly.

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?

Covers actions, pagination, ordering, search, and scope. No output schema, but describes return as 'simple id/name records'. Lacks details on default limit but schema covers that.

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?

Schema coverage is 100% with descriptions; description adds specific searchable fields ('name, id') and valid order_by values, adding value beyond the schema.

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?

Specifies verb 'Read' and resources 'stock locations and stock areas'. Distinguishes from sibling tools by domain and lists four concrete actions. Clear and specific.

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?

No explicit guidance on when to use this tool vs alternatives among siblings. Prerequisite scope is stated, but no when-to-use or when-not-to-use comparisons.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mydata-ag/bexio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server