OpenAccountants

Read more sections of a skill

get_skill_sections

Read-onlyIdempotent

Follow-up to get_skill: fetch sections it listed in section_index as not inlined (for example a supplier-pattern library). Pass section_index for one section, or omit it to get every section with its heading and markdown.

Input Schema

Name	Required	Description
`slug`	Yes	Skill slug
`section_index`	No	Optional. Return only this section (matches the `index` from get_skill's `section_index`).
`section_indices`	No	Optional. Return only these sections.

Output Schema

Name	Required	Description
`slug`	Yes
`version`	No
`sections`	Yes
`key_facts`	No	Optional at-a-glance facts — present only where the skill carries a structured key_facts block; omitted otherwise.
`guardrails`	No
`next_action`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJun 2, 2026
- addedOutput schema / properties / guardrails
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / next_action
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedJun 2, 2026

addedInput schema / properties / section_index

Added value: +{
+  "description": "Optional. Return only this section (matches the `index` from get_skill's `section_index`).",
+  "type": "integer"
+}

addedInput schema / properties / section_indices

Added value: +{
+  "description": "Optional. Return only these sections.",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}

Changed1 schema field changedJun 2, 2026

addedOutput schema / properties / key_facts

Added value: +{
+  "description": "Optional at-a-glance facts — present only where the skill carries a structured key_facts block; omitted otherwise.",
+  "type": "object"
+}

Changed1 schema field changedMay 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "sections": {
+      "items": {
+        "properties": {
+          "heading": {
+            "type": "string"
+          },
+          "heading_level": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "markdown_content": {
+            "type": "string"
+          },
+          "section_index": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "heading",
+          "markdown_content"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "version": {
+      "type": [
+        "integer",
+        "number"
+      ]
+    }
+  },
+  "required": [
+    "slug",
+    "sections"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.2/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 safety and repeatability are covered structurally. The description adds the useful cross-tool detail that sections are addressed by the indexes get_skill reported, but says nothing about ordering, limits, or behavior when a slug or index does not exist.

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?

Two sentences, front-loaded with the relationship to get_skill and then the parameter behavior. No filler, no restatement of the title or annotations.

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?

An output schema exists, so return values need not be described, and the annotations carry the safety profile for this simple read tool. The only real gap is the unaddressed section_indices parameter, which is minor for a three-parameter read operation.

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%, so the baseline is 3. The description adds genuine cross-tool semantics by tying section_index to get_skill's section_index list, but it never mentions the section_indices (plural) parameter, leaving one of the three parameters unexplained in prose.

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 ('fetch sections') and immediately positions itself relative to the sibling get_skill as a follow-up, so an agent can distinguish it from get_skill without opening either schema. It also defines scope: sections that were listed as not inlined.

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

Usage Guidelines5/5

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

Explicitly names the trigger condition (after get_skill, when sections were flagged as not inlined) and gives the routing rule for the optional parameter: pass section_index for one section, omit to get all. The alternative (get_skill's inlined content) is implicitly and clearly excluded.

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

All OpenAccountants 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.