Revly

Hent vurderinger av granskningsfunn

hent_funnvurderinger

Read-onlyIdempotent

Henter vurderingsloggen for granskningsfunn på én eksplisitt oppdrags-ID: funnkode, status, kommentar, tidspunkt, navn og rolle. E-post, personnummer og fødselsdato er ikke med. siden gir bare vurderinger etter tidsstempelet, eldste først. Er truncated true, kall igjen med siden satt til siste opprettet_at. Dette setter ingen vurdering og endrer ikke funnstatus. Høyst 80 rader.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "oppdrag_id": "<oppdrag_id>"
    },
    "name": "hent_funnvurderinger"
  }
}

Input Schema

Name	Required	Description
`siden`	No	Eksklusivt tidspunkt. Rader på nøyaktig dette tidspunktet gjentas ikke.
`status`	No	Bare vurderinger med denne statusen, for eksempel trenger_mer.
`oppdrag_id`	Yes	Eksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.

Output Schema

Name	Required	Description
`siden`	No	Exclusive timestamp the caller sent. Rows at that exact time are not repeated.
`status`	Yes	Result status. not_found_or_unavailable means the engagement is not visible to this connection and the call is an error.
`sources`	No	Sources that contributed to the result.
`evidence`	No
`revly_url`	No	Link to the granskningsfunn page.
`truncated`	No	True when more assessments exist. Call again with siden set to the last opprettet_at.
`oppdrag_id`	No	Engagement ID, as text.
`vurderinger`	No	Assessments after siden, oldest first, at most 80.
`operation_id`	Yes	Revly operation ID for this read, recorded in the access log.
`missing_sources`	No	Sources with no record. Missing data stays visible and is never treated as a positive result.
`vurdering_antall`	No	Matching assessments. Zero means none recorded after the filter.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context beyond them: a hard cap of 80 rows, oldest-first ordering, cursor semantics for 'siden', explicit exclusion of e-post/personnummer/fødselsdato, and confirmation that no finding status is mutated.

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?

Dense, front-loaded and free of filler; every sentence carries operational information. The inline field list slightly duplicates what the output schema already provides, and the telegraphic lowercase sentence openings make it a touch hard to scan.

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?

Covers everything an agent needs to call it correctly: mandatory explicit ID, filterable status, ordering, row cap, truncation handling, and PII scope. Return-value detail is backed by an output schema, so nothing essential is missing.

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%, so the baseline is 3; the description earns above that by explaining the cursor behaviour ('siden gir bare vurderinger etter tidsstempelet') and how to chain it with 'siste opprettet_at' after truncation, which the schema does not convey.

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 ('henter vurderingsloggen for granskningsfunn') scoped to one explicit oppdrag-ID, and enumerates the returned fields so an agent can tell it apart from hent_funn (which returns the findings themselves). The negative framing ('setter ingen vurdering og endrer ikke funnstatus') further separates it from any write path.

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 clear preconditions ('Oppslag uten ID er ikke tillatt') and an explicit retry procedure when truncated is true. It does not name the sibling tool to use for creating assessments, so the 'when not to use' side is implied rather than stated.

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?