Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

Get a review

heliyos_reviews_get
Read-onlyIdempotent

Fetches a single review by ID with its proposal, reasoning, draft email or deal field changes, related records, and decision outcome so users can evaluate and decide on it.

Instructions

Fetches one review by id with everything a person needs to decide it: the worker's proposal and reasoning, the draft email (subject, recipients, body) or the deal's fields before and after, the records and run it belongs to, and, once decided, the comment and outcome. Long texts are cut at 400 characters in concise. Returns structuredContent {review}.

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": {
      "review_id": "<review_id>"
    },
    "name": "heliyos_reviews_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_idYesreview_id: a 24-character hex id.
response_formatNo"concise" (default) returns the proposal with shortened texts; "detailed" returns full texts, the raw proposed arguments and the outcome.concise

Output Schema

NameRequiredDescriptionDefault
reviewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds useful behavior: the truncation rule at 400 characters in concise mode, the fuller contents in detailed mode, and the fact that decision data appears only once the review is decided, plus the structuredContent {review} return shape.

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?

A single front-loaded sentence that spends its length on the payload contents and the truncation caveat; nothing is redundant. It is dense but every clause carries information an agent would otherwise have to discover by calling the tool.

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 two-parameter read tool with full schema coverage, complete annotations, and an output schema, the description covers everything needed to select and call it correctly. The only shortfall is the missing routing to the decide/list siblings, which keeps it just short of full marks.

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 already 100%, so a baseline of 3 applies. The description earns an extra point by adding a fact the schema omits: texts are cut at 400 characters in concise mode, which concretely explains the real cost of the default response_format.

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?

The description names a specific verb and resource ("Fetches one review by id") and enumerates exactly what is returned: the worker's proposal and reasoning, the draft email or before/after deal fields, the parent records/run, and the decision comment and outcome. That level of detail makes it immediately distinguishable from heliyos_reviews_list (many reviews) and heliyos_reviews_decide (acting on one).

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?

Usage is only implied: the phrase "everything a person needs to decide it" hints this is the inspection step before heliyos_reviews_decide, but neither that sibling nor heliyos_reviews_list is named, and there is no explicit when-to-use or when-not-to-use statement.

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

Deploy Server

Other Tools