Skip to main content
Glama

Energy North Journal

Read a guide

get_guide
Read-onlyIdempotent

Read the full text of one Energy North guide by its link.

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": {
      "url": "<url>"
    },
    "name": "get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe guide link, e.g. https://energynorth.blogspot.com/2026/10/...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that the entire 'full text' is returned rather than a snippet, which is meaningful for an agent deciding between this and a search result, but it says nothing about failure modes for invalid links.

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?

A single twelve-word sentence with zero filler, front-loading the verb and the distinguishing detail ('full text of one'). Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with rich annotations and a documented schema, the definition is minimally sufficient. It is thin, however, on what 'full text' includes (metadata, images, truncation) and what happens if the link is stale or from a different site.

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% and the url property already carries a format example, so the schema does the heavy lifting. The description only echoes 'by its link', adding no constraint or format detail beyond the schema; baseline 3 applies.

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 names a specific verb (read) and resource (full text of one Energy North guide) with the identifying key (its link). It implicitly separates itself from listing/searching siblings like latest_guides and search_guides by specifying 'one' guide's 'full text', though it never names an alternative.

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 implied rather than stated: an agent can infer this is the tool to call once it already has a guide URL. There is no explicit when-to-use or when-not guidance, and no mention that search_guides or latest_guides should be used first to obtain the link.

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