Skip to main content
Glama

Recommend a house

recommend
Read-onlyIdempotent

Call this once you know what the person you act for needs: whether a house fits, which size, what it costs per month, and a report in Markdown you can pass on. It advises against a house where one is the wrong choice. Name every need that applies, from this vocabulary. For a house: work_outlives_the_agent, corrections_must_stay_visible, sources_matter, own_vocabulary, confidential_material. Against: only_user_preferences_across_chats, only_retrieval_over_text, millisecond_answers_at_high_volume, running_jobs_or_compute, nobody_will_model. Deciding the size: one_person, an_organization, data_must_stay_in_own_network, scanned_documents, names_found_automatically, large_material. Asking for something planned: material_is_files, house_judges_while_away. Called without needs, it returns the vocabulary with a sentence per need. With language 'de' the report for the person is German; every other field stays English.

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

Input Schema

NameRequiredDescriptionDefault
needsNoThe needs that apply, as words of the vocabulary. Omit to get the vocabulary.
data_gbNoHow much material there is, in gigabytes, if you know. Used to calculate additional volume.
languageNoLanguage of 'report', the text for the person: 'en' or 'de'. Default 'en'. Every other field stays English.en
in_your_wordsNoOptional: what the person asked you for, in one or two sentences of your own. It is recorded so that we learn which questions we did not foresee. It is not interpreted and does not change the answer.

Output Schema

NameRequiredDescriptionDefault
gapsYesWhat you asked for that is not available yet, the most important first.
sizeYesThe size of house that follows from the needs today. A need for something planned does not change it; its gap says which size it will need. Null when a house does not fit or no need was named.
citesYesThe topics this answer rests on, each with the hash of its body.
priceYesWhat the recommended house costs. Null when a house does not fit or no need was named.
manualYesThe version of the manual; the report cites it.
reportYesThe report for the person you act for, in Markdown, ready to pass on. Empty when no need was named.
reasonsYesOne entry per need you named: what it means for a house, and the topic that backs it.
verdictYes'fits', 'fits_with_gaps', 'does_not_fit', or 'say_what_you_need' when no need was named.
next_stepsYesWhat to call next.
vocabularyYesThe needs you can name. Filled only when you named none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: it may advise against a house, returns a Markdown report, and changes behavior when needs are omitted or language is German.

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?

The definition is front-loaded and most sentences carry needed information, especially the vocabulary lists. It is somewhat dense and list-heavy, but not padded with irrelevant content.

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?

Given the presence of an output schema and covering annotations, the description is complete for correct invocation: it explains the needs vocabulary, no-needs behavior, data volume, language handling, and report delivery.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is already high, the description supplies the actual needs vocabulary and categorizes the words, which the schema does not enumerate. It also clarifies data_gb usage and that in_your_words is recorded but not interpreted.

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?

The description states a clear verb (recommend) and resource (house), plus specific outputs: fit, size, monthly cost, and a Markdown report. It does not explicitly distinguish itself from siblings such as request_house or house_status, so it falls short of a 5.

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?

It says when to call: once you know the person's needs, and notes that calling without needs returns the vocabulary. It does not explicitly compare against request_house or explain when recommendation should precede a request, so it is clear but not fully route-guiding.

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