Skip to main content
Glama
Sign In
edhec-mcp

edhec-mcp

by Sillvs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Grades and due dates

bb_grades
Read-onlyIdempotent

Retrieve a course's gradebook items, including due dates, point values, and your visible grades, to track assignments and grades.

Instructions

Gradebook items of a course with due dates, points and your own grade where visible.

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": {
      "course": "<course>"
    },
    "name": "bb_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYesCourse: internal id like "_12345_1", a course URL, or the course code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: grades are only shown "where visible", implying permission-dependent partial results. It does not say whether the call is scoped to a single course or what happens for an invalid course, and there is no output schema to compensate.

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?

One sentence fragment with no filler, and the returned fields are listed compactly. It loses a point because the missing verb makes it read as a label rather than a statement of action, which slightly hurts front-loading of intent.

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 read-only, one-parameter tool with no output schema, the description does tell the agent what data comes back (due dates, points, own grade) and flags conditional visibility. It is still thin on scope (single course only?) and on behavior for inaccessible or unknown courses, which matters given the open-world hint.

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 single course parameter already documents accepted forms (internal id, URL, or course code), so the schema carries the full parameter burden. The description adds no extra meaning about the course argument, which is acceptable at baseline for one fully documented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "Gradebook items of a course with due dates, points and your own grade where visible" names the resource and the fields returned, but no verb, so the agent must infer that this is a read/list operation. It also does not distinguish the tool from look-alike siblings such as bb_course_contents or bb_upcoming, which also surface course-level data including due dates.

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?

There is no guidance on when to call this versus bb_upcoming (which also deals with due dates) or bb_course_contents. The description states content but never says when this tool is the right choice or what its scope limits are.

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