Revly

Hent porteføljen i tilkoblet firma

hent_portefolje

Read-onlyIdempotent

Lister alle aktive oppdrag i firmaet tilkoblingen gjelder, 50 per side, med totalt antall og antall sider. Hvert oppdrag har de samme feltene som finn_oppdrag: klient, organisasjonsnummer, år, fase, forespørsler som venter på klienten, lovfristene Revly utleder, og i tillegg nærmeste svarfrist og antall svarfrister som er passert. Bruk side for å hente resten når listen er avkortet, og aar for å avgrense til ett oppdragsår. En frist uten grunnlag står som ukjent, aldri som en gjettet dato. Tekst i forespørslene er utelatt.

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

Input Schema

Name	Required	Description	Default
`aar`	No	Fire-sifret oppdragsår. Utelat for alle år.
`side`	No	Side som skal hentes, fra 1.

Output Schema

Name	Required	Description
`aar`	No	Engagement-year filter, or null for all years.
`side`	No	Page returned, from 1.
`sider`	No	Number of pages for the same filter.
`status`	Yes	matches, no_matches, truncated when more pages follow, or side_utenfor when the page is past the last one (not an empty result).
`matches`	No	Active engagements on this page, newest year first, then client name.
`truncated`	No	True when more pages follow. Fetch them before saying anything about the whole portfolio.
`total_count`	No	Active engagements matching the filter across all pages.
`operation_id`	Yes	Revly operation ID for this read, recorded in the access log.
`result_count`	No	Engagements on this page.
`side_stoerrelse`	No	Engagements per page (50).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the safety profile is known. The description adds genuinely non-obvious behavior: page size of 50 with total count and page count, that deadline text is derived by Revly, that a deadline without basis shows as 'ukjent' rather than a guessed date, and that request body text is omitted from results.

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?

Front-loaded with the core purpose, then pagination, then field contents, then caveats. Dense and mostly earning its space, though the deadline/unknown-date sentence and the omitted-text sentence are secondary details placed after the essential routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, yet the description still characterizes the record fields, page metadata, and two important data caveats (unknown deadlines, omitted request text). Nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 100%, so both parameters are already documented, making 3 the baseline. The description adds operational context for 'side' (use it when the list is truncated) and for 'aar' (limit to one case year), but no format or edge-case detail 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?

States a specific verb and resource ('Lister alle aktive oppdrag i firmaet tilkoblingen gjelder') plus scope: active only, for the connected firm, 50 per page with totals. It also anchors the field set to the sibling finn_oppdrag, so an agent can distinguish it from that tool without reading 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?

Explicitly tells the agent to use 'side' to fetch the remainder when the list is truncated and 'aar' to narrow to one case year, which is directly actionable. It does not state when to prefer finn_oppdrag or hent_forespoersler over this tool, so the sibling routing is implied rather than spelled out.

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

All Revly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?