Skip to main content
Glama
pennyleans

cint MCP Server

by pennyleans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
cint_search_docsB

Search across cint 0.2.0 specifications (SPEC-00P to SPEC-09P), GLOSSARY, ERRATA, and University curriculum (CU-000 to CU-401). Compact output by default.

cint_get_docA

Retrieve one self-contained specification or curriculum chunk by the ID cint_search_docs returns (e.g. 'spec-04p:scope', 'cu-201-04:muldiv').

cint_lookup_diagnosticA

Explain any compile diagnostic (C1001 to C9102) or runtime fault (E_OVERFLOW to E_ASSERT) with before/after fixes.

cint_get_recipeB

Fetch a verified cint 0.2.0 code recipe (fixed-point-trig, fixed-point-ln-sqrt, wide-i1024-scaling, svg-generator, fnv1a-digest, money-ledger, kernel-double-buffer) with digest.

cint_list_curriculumC

List available cint University lessons (CU-000.2 to CU-401.2).

cint_checkA

Compile cint (.ci) source without running it (cint emit-c) and return its CINT-DIAG-1 diagnostics, or 'compiles'. Needs a local cint (PATH or CINT_PATH); look codes up with cint_lookup_diagnostic.

cint_evalA

Compile and run a cint (.ci) program (cint run) and return its output, or its CINT-DIAG-1 diagnostic or CINT-FAULT-1 fault record. A program is void main() { ... } or top-level statements. Needs a local cint (PATH or CINT_PATH).

cint_testA

Run the test "name" { ... } blocks of cint (.ci) source (cint test) and return one CINT-TEST-1 line per test, with the fault record of each failure. Needs a local cint (PATH or CINT_PATH).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
cint 0.2.0 Edition & Toolchain Manifest
cint for C Programmers (CU-000.2)
cint for Python and NumPy Programmers (CU-000.2)
cint 0.2.0 Language & Built-in Cheat Sheet
cint 0.2.0 Compiler Refusals (SPEC-09P.1 Clause 12)
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct action on a distinct resource: check (compile only), eval (compile+run), test (run test blocks), lookup_diagnostic (explain codes), search_docs vs get_doc (find vs retrieve), get_recipe, list_curriculum. The descriptions explicitly disambiguate the easily confused compile/run/test trio and the search/get doc pair.

Naming Consistency4/5

All tools share the cint_ prefix and snake_case, and most follow verb_noun (lookup_diagnostic, get_recipe, list_curriculum, search_docs, get_doc). The bare verbs check, eval, and test deviate slightly from the pattern but remain readable and unambiguous.

Tool Count5/5

Eight tools is well-scoped for a language-tooling server: execution (check/eval/test), documentation discovery (search_docs/get_doc), diagnostics explanation, and curated assets (recipes/curriculum). Each tool earns its place with no filler.

Completeness4/5

The surface covers the full core workflow of compiling, running, testing, diagnosing, and looking up docs/recipes/lessons. Minor gaps exist (no version/environment info tool, no formatter or project scaffolding), but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources