Skip to main content
Glama

Course syllabus metadata

bpj_course_syllabus_metadata
Read-onlyIdempotent

Build Course metadata with a provider, language and syllabus topics from individual lines.

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": {
      "name": "<name>",
      "provider": "<provider>",
      "language": "<language>",
      "topics": "<topics>"
    },
    "name": "bpj_course_syllabus_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
topicsYes
languageYes
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral rule — topics are supplied 'from individual lines' — but says nothing about the output shape or whether inputs are validated/normalized.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or repetition. It is efficient, though it could have used one more short clause on the produced output without becoming bloated.

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?

With four required parameters, no output schema and no annotation describing the return value, the definition leaves the agent guessing what 'Course metadata' actually looks like when returned. For a pure computation tool whose entire value is its output format, that is a meaningful gap.

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 0%, so the description carries the burden, and it does add the non-obvious semantic that the topics string is newline-delimited. However it omits the 'name' parameter entirely and gives no hint about the expected form of the 'language tag' (e.g. BCP 47), leaving half the parameters underexplained.

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 concrete verb and resource ('Build Course metadata') and names the inputs that define the result (provider, language, syllabus topics). 'Course' distinguishes it from the ISBN, podcast, recipe and other metadata siblings. It stops short of saying what artifact is produced (JSON-LD, HTML snippet, structured object), which keeps it off a 5.

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?

The description gives no when-to-use guidance, no prerequisites, and no routing to or away from the many sibling *_metadata tools. An agent must infer from the name alone that this is the Course-flavoured member of a metadata-generation family.

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.