Skip to main content
Glama

Frisian MCP (Django)

by com.frisian-mcp
OverviewDiscussionsAdmin

docs

Start here — frisian-mcp documentation and server guide. Actions: about (server identity and links), getting_started (step-by-step adoption guide), integrations (Django/DRF config reference), security (auth model, OAuth, API keys, tiers), demo (explore the live demo endpoints), documents (browse all documentation articles), rag (semantic and full-text doc search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
pageNo
actionNoOperation to perform. Omit or use 'help' to list all available actions and their required parameters.
paramsNoAction-specific parameters. about: {version}; getting_started: {version}; integrations: {version}; security: {version}; demo: {surface}; documents: {sub_action, slug, id, category, limit, offset}; rag: {query, limit, offset, category}. 'mode', 'page', 'page_size' and 'filter_keys' are top-level ONLY on a continuation call (i.e. alongside a 'continuation_token'); otherwise they are ordinary action parameters and belong here.
page_sizeNo
filter_keysNo
continuation_tokenNoFrom a probe response. Send at the TOP LEVEL, not inside 'params'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / continuation_token
      Added value: +{
+  "description": "From a probe response. Send at the TOP LEVEL, not inside 'params'.",
+  "type": "string"
+}
    • addedInput schema / properties / filter_keys
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "enum": [
+    "summary",
+    "paginated",
+    "filtered",
+    "full"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "type": "integer"
+}
    • changedInput schema / properties / params / description
      Previous value: -"Action-specific parameters. about: {version}; getting_started: {version}; integrations: {version}; security: {version}; demo: {surface}; documents: {sub_action, slug, id, category, limit, offset}; rag: {query, limit, offset, category}."New value: +"Action-specific parameters. about: {version}; getting_started: {version}; integrations: {version}; security: {version}; demo: {surface}; documents: {sub_action, slug, id, category, limit, offset}; rag: {query, limit, offset, category}. 'mode', 'page', 'page_size' and 'filter_keys' are top-level ONLY on a continuation call (i.e. alongside a 'continuation_token'); otherwise they are ordinary action parameters and belong here."
  2. Changed1 schema field changed
    • changedInput schema / properties / params / description
      Previous value: -"Action-specific parameters. about: (no params); getting_started: (no params); integrations: (no params); security: (no params); demo: {surface}; documents: {sub_action, slug, id, category, limit, offset}; rag: {query, limit, offset, category}."New value: +"Action-specific parameters. about: {version}; getting_started: {version}; integrations: {version}; security: {version}; demo: {surface}; documents: {sub_action, slug, id, category, limit, offset}; rag: {query, limit, offset, category}."
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does list the available actions and their purposes, which is useful, but it does not state whether operations are read-only, how the help flow works, how pagination or continuation tokens behave, or what side effects or auth dependencies exist.

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?

The description is a single dense, front-loaded sentence with no filler. The action list is compact and each phrase earns its place, though it could have been slightly clearer as a structured list rather than a long comma-separated run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a routing-style tool with 7 parameters, nested objects, and continuation-token mechanics, yet there is no output schema or annotation support. The description covers only action names and omits the invocation patterns needed for pagination, continuation calls, and mode behavior, leaving an agent under-equipped without deep schema inspection.

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 only 43%, and the description itself does not compensate for the gap. It mentions action names but never explains top-level parameters like mode, page, page_size, filter_keys, or continuation_token, which have non-obvious rules around continuation calls and placement inside params.

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?

The description clearly identifies the tool as the entry point to frisian-mcp documentation and server guide, and enumerates seven concrete actions with one-line semantic labels. This distinguishes it from siblings like demo, install, and troubleshooting. It loses a point because 'Start here' is an orienting instruction rather than a specific verb+resource statement.

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

Usage Guidelines3/5

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

'Start here' implies this tool should be used first, giving some usage context. However, there are no explicit when-to-use versus when-not-to-use statements, and the description does not clarify when to use the docs tool's demo action versus the sibling demo tool.

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

All Frisian MCP (Django) toolsInspect
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.

Resources