Homesage.ai MCP

Get Portal Guide Section

get_portal_guide_section

Read-only

Read one Homesage.ai portal guide section — how-to help for the Homesage.ai web portal. Free. Pass a section_id from list_portal_guide_sections. The guide names every screen, button and filter by its on-screen label.

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": {
      "section_id": "<section_id>"
    },
    "name": "get_portal_guide_section"
  }
}

Input Schema

Name	Required	Description	Default
`section_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint=false) and an output schema exists, so the description's added value is the "Free" cost note and the warning that the guide's wording mirrors on-screen labels. That label-matching detail is genuinely useful for interpreting results. Return format and size are not discussed, which is acceptable given the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and resource, then the usage prerequisite, then the content caveat. No filler or redundant restatement of the title.

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?

For a single-parameter read-only tool with an output schema and full annotation coverage, everything an agent needs to invoke it correctly is present: the resource, the ID source, the cost, and how to read the returned labels.

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 description coverage is 0%, so the description must carry the parameter meaning — and it does by naming section_id and, more importantly, telling the agent where to source valid values (list_portal_guide_sections). It stops short of stating the ID format or whether the call fails on unknown IDs.

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 ("Read one Homesage.ai portal guide section") and immediately scopes it as how-to help for the web portal. The phrase "one ... section" plus the pointer to list_portal_guide_sections distinguishes it cleanly from the sibling listing tool.

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 a clear prerequisite workflow: pass a section_id obtained from list_portal_guide_sections, and notes the call is free. It does not explicitly say when to prefer this over the sibling list tool, but the one-vs-many relationship is inferable from the description.

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

All Homesage.ai MCP 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?