Skip to main content
Glama

RealMarket Review Time

Estimate literature review time

estimate_literature_review_time
Read-onlyIdempotent

Calculates the hours spent screening titles and abstracts and reading full texts, per review and per year, the share of each stage, the extra effort of double screening and, when an hourly cost is given, the yearly cost in Brazilian reais.

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_type": "<review_type>",
      "reviews_per_year": "<reviews_per_year>",
      "records_found": "<records_found>",
      "minutes_per_record_screening": "<minutes_per_record_screening>",
      "full_texts_read": "<full_texts_read>",
      "minutes_per_full_text": "<minutes_per_full_text>",
      "reviewers_per_record": "<reviewers_per_record>"
    },
    "name": "estimate_literature_review_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
review_typeYesKind of review.
records_foundYesRecords returned by the database search of one review.
full_texts_readYesFull texts read per review.
hourly_cost_brlNoOptional cost of one hour of work, in BRL.
reviews_per_yearYesReviews the group runs per year.
reviewers_per_recordYesHow many people screen each record.
minutes_per_full_textYesMinutes to read and extract one full text.
minutes_per_record_screeningYesMinutes to screen one title and abstract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuine behavioral detail about what is computed: per-review and per-year hours, stage shares, the extra effort of double screening, and cost only 'when an hourly cost is given'. It does not disclose assumptions, defaults, or units of rounding.

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 with the core action first and outputs enumerated after. Dense but no filler; the trailing Brazilian-reais clause earns its place by fixing the currency.

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?

There is no output schema, so describing the returned quantities is exactly what this description must do, and it does so comprehensively: stage hours, per-review and per-year totals, stage shares, double-screening overhead, and conditional cost. An agent can judge from the description alone whether the result answers its question.

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 coverage is 100%, so every parameter and its bounds are already documented. The description adds modest meaning by tying hourly_cost_brl to the optional cost output and reviewers_per_record to 'double screening', but it explains no syntax or interaction beyond that. Baseline 3 is correct.

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?

Opens with a specific verb and resource — 'Calculates the hours spent screening titles and abstracts and reading full texts' — and then enumerates the computed outputs. The purpose is unambiguous, though the enumeration crowds out a single crisp statement of intent.

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?

No explicit when-to-use or when-not-to-use guidance, and no prerequisites or alternatives named. Usage is only implied by the output list (a planning/estimation aid). With no sibling tools the cost of this gap is low, but the guidance itself is absent.

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