Skip to main content
Glama

Get content item

bb_get_content
Read-only

Retrieves a course content item with its body text, file metadata, links, due date and permissions, so you can read assignment or material details by course and content ID.

Instructions

Get one content item with its body text, file metadata, posted links, due date and permissions. Read file contents with bb_get_attachment.

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": {
      "courseId": "<courseId>",
      "contentId": "<contentId>"
    },
    "name": "bb_get_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes
contentIdYes

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 and openWorldHint=false, so the safety profile is covered structurally. The description adds the useful signal that this is a rich composite read (body, metadata, links, due date, permissions), but says nothing about access restrictions — e.g. whether permissions returned reflect the caller's own rights or all viewers — or about behavior when the item is missing or inaccessible.

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 short sentences with no filler: the capability and its returned fields come first, the sibling routing pointer second. Every clause carries information an agent can act on.

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?

With no output schema, the description usefully previews the return payload (body text, file metadata, links, due date, permissions) and annotations cover the read-only profile. The remaining gap is the unexplained required identifiers, which matters for a two-parameter lookup tool.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters (courseId, contentId) are undocumented in structured data and the description must compensate. It does not: it never explains that courseId scopes the lookup or that contentId identifies the single item, leaving an agent to infer both from names alone.

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?

States a specific verb and resource ("Get one content item") and enumerates what comes back: body text, file metadata, posted links, due date, permissions. It separates itself from bb_get_attachment by routing file-content reads elsewhere. It does not distinguish itself from bb_get_course_content or bb_list_content, so the sibling picture is only partly drawn.

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?

The sentence "Read file contents with bb_get_attachment" is an explicit when-not plus a named alternative, which is real routing guidance. However, no guidance is given on when to use this single-item fetch versus the list/bulk variants (bb_get_course_content, bb_list_content), leaving the main ambiguity unaddressed.

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