Skip to main content
Glama

Vinka

Mina bolag

lista_bolag
Read-onlyIdempotent

Listar bolagen som Vinka sköter åt dig, med bolag_id att använda i övriga verktyg.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description usefully adds that the response contains a bolag_id field for reuse in other calls, which matters since there is no output schema, but it says nothing about ordering, pagination, or the other fields each company carries.

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?

A single short sentence with no filler, front-loading the resource and appending the actionable detail (bolag_id for other tools). Every clause carries information.

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 zero-parameter read tool with full annotation coverage, the description covers the essentials and even names the key return field despite having no output schema. Minor gaps remain: what each company record contains and whether the list is exhaustive or paged.

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 meaning to convey; the baseline of 4 applies. Nothing in the description misdescribes or omits input semantics.

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?

States a specific verb and resource ("Listar bolagen som Vinka sköter åt dig") and clarifies the useful output, bolag_id. This clearly distinguishes it as the company-enumeration tool, though it does not name a specific sibling it contrasts with — none of the listed siblings appears to overlap directly.

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 clause "med bolag_id att använda i övriga verktyg" implies this tool should be called to obtain IDs needed elsewhere, which is real contextual guidance. However, it stops short of stating an explicit when-to-use rule (e.g. "call this first") or any exclusions.

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.