Skip to main content
Glama

Firmendaten des verbundenen Kontos

get_profile
Read-onlyIdempotent

Return the company profile of the connected facturo account: name, address, UID, bank details and plan. Needs a connected account. Use it to check what the real invoice will carry as sender before creating one. Also the way to connect: when the user wants to link their facturo account or save invoices in facturo, call it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: a connected account is a prerequisite, and calling it is also the entry point for linking an account — worth knowing since that implies an auth/consent flow not expressed in annotations.

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?

The purpose and the returned fields are front-loaded in the first sentence, followed by concise usage triggers. The final sentence ('Also the way to connect...') is slightly run-on and shifts topic abruptly, but nothing is redundant.

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?

With no output schema, the description carries the return-value burden and does so by listing the profile fields. It also notes the connected-account prerequisite; only the shape of the failure case when no account is linked is left implicit.

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 parameters, so there is no schema semantics to supplement; the baseline applies. The description correctly does not invent parameter language and instead spends its words on what the call returns.

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 and resource ('Return the company profile of the connected facturo account') and enumerates the fields returned (name, address, UID, bank details, plan). The read-oriented wording makes it distinguishable from the sibling update_profile without opening either schema.

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?

Gives concrete when-to-use triggers: check the sender data before creating an invoice, and link a facturo account when the user wants to connect or save invoices there. No explicit when-not or named alternative (e.g. update_profile), so it stops short of full routing guidance.

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