Skip to main content
Glama
Sign In
organisation.md

organisation.md

by shashank-sn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

read_section

Read-only

Retrieve any section from organisation.md by providing the heading name. Quickly access specific content like 'Team' or 'Identity' without reading the whole file.

Instructions

Read a specific section from organisation.md by heading name.

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": "<section>"
    },
    "name": "read_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesThe section heading to read (e.g., 'Team', 'Identity')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds minimal behavioral context beyond restating the read operation. No contradictions. Additional details like handling of missing headings could improve transparency.

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?

Single sentence, front-loaded with verb and resource, no superfluous words.

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 simple read operation with one parameter and annotations present, the description is mostly complete. Lacks specifics on heading matching (e.g., case sensitivity, exact format), but adequate for common use.

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 description coverage is 100% for the single parameter 'section', which includes an example. The tool description merely echoes 'by heading name', adding no new semantics beyond the schema.

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 clearly states the action (read), the resource (specific section from organisation.md), and the method (by heading name). It distinguishes from siblings like 'read_org' which reads the whole file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives such as 'read_org', 'search_context', or 'update_section'. The description does not mention exclusion criteria or alternative tools.

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