tech.kaiku/kaiku

Est-ce que tech.kaiku/kaiku est sûr ?

Au dernier audit MCP Hub, le serveur MCP « tech.kaiku/kaiku » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 143 outils

• add_attachment≈ 382 tokens

  Attach a file to an issue: pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Attaching a filename the issue already has replaces that file rather than adding a second copy, so retrying this call cannot double it. A file on the person's own disk — a screenshot, a PDF — is better attached by path through the pm-files MCP server than typed out as base64; local_files_setup says how to connect it. Returns the attachment's download URL. Requires permission to edit issues in that project.

  Paramètres, retour & exemple (5)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • text · string|null · optionnel
    The file's content as text, stored as UTF-8 — for a log, CSV or Markdown file you are writing here. Alternative to 'contentBase64'; passing both is refused.
  • filename · string · requis
    File name to store, e.g. 'report.pdf'. Any directory part is dropped.
  • mimeType · string|null · optionnel
    Content type to record for the listing, e.g. 'text/csv'. Ignored when the bytes identify themselves (a PNG is a PNG whatever you call it), and never used to serve the file.
  • contentBase64 · string|null · optionnel
    The file's bytes, base64-encoded (a 'data:…;base64,…' URL is accepted and unwrapped). Use 'text' instead when the file is text.

  Exemple d'appel

  {"name": "add_attachment", "arguments": {"key": "texte", "filename": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_comment≈ 411 tokens

  Add a comment to an issue, or reply to one of its comments ('replyTo' is a comment id from get_comments). A reply notifies the author of the comment it answers, whether or not they watch the issue — no mention needed — and they are told once even if also mentioned. Requires permission to comment in that project (read-only members cannot). Answers with 'notified' (who this actually reaches, the answered author included), 'answered' (for a reply: whose comment it answers, and 'notified' false with a 'reason' when they are not told) and 'unresolvedMentions' (what looked like a mention and reached nobody, each with a reason) — a wrong handle is stored as written and never refused, so that list is the only sign it did not land. Where the workspace has agents, [~agent:role] (e.g. [~agent:product]) calls one to answer in the thread on your behalf: 'agents' lists each call with its requestId and status, and an agent that will not come is in 'unresolvedMentions' with its reason (agent_unknown, agent_off, agent_plan, agent_budget, too_many).

  Paramètres, retour & exemple (3)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • body · string · requis
    Comment body. Markdown is kept as written, and carries $…$ / $$…$$ LaTeX formulas and [~username] mentions (the username, which list_users hands you ready-made — never the display name).
  • replyTo · integer|null · optionnel
    The comment this one answers, as returned by get_comments — on the same issue and not deleted.

  Exemple d'appel

  {"name": "add_comment", "arguments": {"key": "texte", "body": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_legal_reference≈ 376 tokens

  Put a reference to a legal act on an issue or a wiki page — as «Add» in the block «Legal acts» does: it is yours, accepted at once. 'url' is the act's address on one of the official sites acts are read from (a refusal lists them); an act not read yet is read in the background, so 'hasText' may be false at first. 'place' is the place in the act in words («Article 18»). With 'commentId' the reference stands in that comment instead of the issue's or the page's own text. The same place of the same act already there is that reference ('added' false). Requires permission to edit the issue or the page — to comment, for a comment's — and a project that keeps legal references.

  Paramètres, retour & exemple (5)

  Paramètres

  • url · string · requis
    The act's address, e.g. 'https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32015L0849'.
  • page · integer|null · optionnel
    Wiki page id. Either this or 'issue'.
  • issue · string|null · optionnel
    Issue key, e.g. 'UK-1'. Either this or 'page'.
  • place · string|null · optionnel
    The place in the act, in words, e.g. 'Article 18'.
  • commentId · integer|null · optionnel
    A comment on that issue or page the reference stands in (an id from get_comments), instead of the issue's or the page's own text.

  Exemple d'appel

  {"name": "add_legal_reference", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_wiki_attachment≈ 569 tokens

  Attach a file to a wiki page, identified by 'pageId' or by 'spaceKey' + 'title': pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Re-attaching a filename the page already has replaces its bytes and bumps its version, as the wiki does everywhere else, so retrying this call cannot leave two copies. A file on the person's own disk — a screenshot, a PDF — is better attached by path through the pm-files MCP server than typed out as base64; local_files_setup says how to connect it. An attached file is not *on* the page until the body references it — the answer hands you the Markdown to add with update_wiki_page. An image may also carry a dark-theme version, attached as the same name with '-dark' before the extension (diagram.svg + diagram-dark.svg); the body still references the plain name. Requires permission to edit the page.

  Paramètres, retour & exemple (8)

  Paramètres

  • text · string|null · optionnel
    The file's content as text, stored as UTF-8 — for a log, CSV or Markdown file you are writing here. Alternative to 'contentBase64'; passing both is refused.
  • title · string|null · optionnel
    Exact page title, when identifying the page by title.
  • pageId · integer|null · optionnel
    Page id (as returned by search_wiki).
  • comment · string|null · optionnel
    Short note about this upload, shown in the page's attachment list.
  • filename · string · requis
    File name to store, e.g. 'diagram.png'. Any directory part is dropped.
  • mimeType · string|null · optionnel
    Content type to record for the listing, e.g. 'text/csv'. Ignored when the bytes identify themselves, and never used to serve the file.
  • spaceKey · string|null · optionnel
    Space key, when identifying the page by title.
  • contentBase64 · string|null · optionnel
    The file's bytes, base64-encoded (a 'data:…;base64,…' URL is accepted and unwrapped). Use 'text' instead when the file is text.

  Exemple d'appel

  {"name": "add_wiki_attachment", "arguments": {"filename": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_wiki_comment≈ 399 tokens

  Comment on a wiki page, or reply to one of its comments ('replyTo' is a comment id from get_wiki_page). A reply notifies the author of the comment it answers, whether or not they watch the page — no mention needed — and they are told once even if also mentioned. Identify the page by 'pageId', or by 'spaceKey' + 'title'. Markdown is rendered; mention someone as [@Their Name](user:username), the wiki's own form. Requires permission to comment in that project. Answers with 'notified' (who this actually reaches, the answered author included), 'answered' (for a reply: whose comment it answers, and 'notified' false with a 'reason' when they are not told) and 'unresolvedMentions' (what looked like a mention and reached nobody, each with a reason) — a wrong handle is stored as written and never refused, so that list is the only sign it did not land.

  Paramètres, retour & exemple (5)

  Paramètres

  • body · string · requis
    Comment body as Markdown, which also carries $…$ / $$…$$ LaTeX formulas.
  • title · string|null · optionnel
    Exact page title, when identifying the page by title.
  • pageId · integer|null · optionnel
    Page id (as returned by search_wiki).
  • replyTo · integer|null · optionnel
    The comment this one answers, as returned by get_wiki_page.
  • spaceKey · string|null · optionnel
    Space key, when identifying the page by title.

  Exemple d'appel

  {"name": "add_wiki_comment", "arguments": {"body": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_bank_transfer≈ 175 tokens

  Administrators only: where a bank transfer is to be sent (PM-625) — beneficiary, account and its own currency, bank and SWIFT, the intermediary bank if there is one, the purpose line, how many days a wire is given, and who last changed all of it. 'offered' is the one flag that answers «may a customer pick a transfer right now»: it is switched on AND carrying everything a payment needs, which is not the same as 'enabled'. A bill already issued carries its own frozen copy of these details and is not changed by what this returns. Amounts are always USD, whatever the account's own currency is.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "admin_bank_transfer", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_errors_week≈ 158 tokens

  Administrators only: the error collector's week — events and distinct errors per project against the week before, errors first seen that week with their release, the loudest by events and by people, and errors that came back after being resolved. The same numbers the weekly error report carries. A project the collector did not answer about has null counts and a reason, never zeros. Ask for an earlier week with weeksAgo.

  Paramètres, retour & exemple (1)

  Paramètres

  • weeksAgo · integer · optionnel
    0 is the last full week, 1 the one before it.

  Exemple d'appel

  {"name": "admin_errors_week", "arguments": {"weeksAgo": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_funnel≈ 542 tokens

  Administrators only: the installation as a business over a period — registrations, how many of them became working companies, purchases and conversion by cohort, churn, and money. Money comes in two halves that must not be added together: 'stock' is what recurs every month at today's prices, 'revenue' is what actually arrived inside the period. Each carries its own currency. Figures come from the fleet's ledger, so 'machines' says how current each machine's copy is — a machine that is behind makes the totals older than they look, it does not make them wrong. 'activation' is how many of the companies registered in the period have had their first agent come in (the first request with a configured token), and how soon — within the hour, the day, the week. 'legal' is the same cohort narrowed to the companies that came for the law — the owner signed up through a page for lawyers, or the company was made with the requirements register — as four counts: registered, a project keeps legal references, a legal document's card opened in the first week, the add-on paid for. Its 'withReferences' is null and 'unknown' names the machines while they have not reported the switch — never zero. 'ai' is AI as money over the same period — what our key's calls cost at each provider, what companies were charged, the margin, the cost nobody was charged for and why, what has accrued and what 'ai' invoices still want — and is neither in 'stock' nor in 'revenue'. Its totals are null, never zero, while a machine has not reported its AI: 'ai.missing' names it and 'ai.reported' is the sum over the machines that did. Default period: the last 90 days.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string|null · optionnel
    End of the period, as YYYY-MM-DD, included. Use with 'from'.
  • days · integer|null · optionnel
    How many days back from today. Defaults to 90, at most 730. Ignored when 'from' and 'to' are given.
  • from · string|null · optionnel
    Start of the period, as YYYY-MM-DD. Use with 'to'.

  Exemple d'appel

  {"name": "admin_funnel", "arguments": {"to": "texte", "days": 1, "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_invoices≈ 250 tokens

  Administrators only: what companies were asked to pay and what answered it — each invoice with its amount, its coin, whether it is paid and what is short, and the payments against it. Amounts are never added across coins: each row carries its own currency and they stay apart. The list is the fleet's ledger, so 'machines' says how current each machine's copy is. One invoice's delivery record belongs to the machine that took the payment and is not rolled up — the answer says so where it is missing rather than showing an empty list.

  Paramètres, retour & exemple (3)

  Paramètres

  • slug · string|null · optionnel
    Only invoices of the company at this address.
  • limit · integer · optionnel
    How many rows, newest first. Default 50, at most 100.
  • status · string|null · optionnel
    Only invoices in this state, e.g. 'open', 'paid', 'void'.

  Exemple d'appel

  {"name": "admin_invoices", "arguments": {"slug": "texte", "limit": 1, "status": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_landing_week≈ 127 tokens

  Administrators only: the landing site's week — visits, where they came from, clicks on sign-up, and the registrations that followed. The same numbers the weekly report carries into the monitoring chat. Ask for an earlier week with weeksAgo. The rendered message is not returned, only the figures.

  Paramètres, retour & exemple (1)

  Paramètres

  • weeksAgo · integer · optionnel
    0 is the last full week, 1 the one before it.

  Exemple d'appel

  {"name": "admin_landing_week", "arguments": {"weeksAgo": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_load≈ 174 tokens

  Administrators only: how loaded this machine is and what the language models cost. Load is this machine's own — database, streams, memory, processor, traffic and stored bytes, each as used against allowed, where an allowance is known. Model spend covers the assistant, search-by-sentence and translation over a rolling window, with totals and breakdowns by feature, by model and by day; costs are estimates from the prices recorded at the time. Who spent it is not returned here.

  Paramètres, retour & exemple (1)

  Paramètres

  • days · integer · optionnel
    Window for model spend, in days. Default 30; 0 means all time.

  Exemple d'appel

  {"name": "admin_load", "arguments": {"days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_overview≈ 159 tokens

  Administrators only: the whole installation by the numbers — accounts, workspaces, projects, issues, comments and sprints, plus issues broken down by status and by project. Counted across every workspace, which is what makes it the installation's rather than one company's. A total is null, never zero, when a machine of the fleet did not answer: 'fleet' says which machines were asked and which are missing, and 'here' is always what this machine counted. The breakdowns are this machine's. Read a null as 'nobody knows', never as 'none'.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "admin_overview", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_set_bank_transfer≈ 762 tokens

  Administrators only, and this one CHANGES things: state where bank transfers are to be sent. Send the WHOLE set every time — anything left out is cleared, not kept, because details half of one bank and half of another are money sent to a mixture of two. Read admin_bank_transfer first and repeat what you are not changing. Switching the method on is refused while anything a payment needs is missing (beneficiary, account, swift, and a purpose line carrying {invoice}), and the refusal names the field; switching it off is never refused. 'minimumUsd' is a floor under the METHOD and not under the debt: a bill below it is offered the other ways to pay, and what is owed does not change. The change is recorded against the calling administrator. Bills already issued keep the details they were issued with.

  Paramètres, retour & exemple (13)

  Paramètres

  • note · string|null · optionnel
    A line for the payer, e.g. which charges are whose. Shown with the details.
  • swift · string|null · optionnel
    The bank's SWIFT/BIC.
  • account · string|null · optionnel
    The account number or IBAN.
  • enabled · boolean · requis
    Whether this installation takes transfers. On is refused while a required field is missing; off never is.
  • purpose · string|null · optionnel
    What the payer must write as the purpose. Has to carry {invoice} — a transfer that does not name its bill arrives as a sum nobody can place. Defaults to 'Invoice {invoice}'.
  • bankName · string|null · optionnel
    The bank's name and address.
  • minimumUsd · number|null · optionnel
    The smallest bill that may be paid by transfer, in USD — correspondent fees eat a small one. Left out there is NO floor, which is the cleared state and not zero; a customer under it is offered the other ways to pay and told why.
  • beneficiary · string|null · optionnel
    Who the money is sent to — the account holder's name as the bank has it.
  • daysToArrive · integer|null · optionnel
    How many days a wire is given to arrive, 1 to 60. The period stays open that long. Left out, the stored number is kept (7 to start with).
  • accountCurrency · string|null · optionnel
    The account's OWN currency, e.g. 'AMD'. Bills stay in USD; this is what the receiving bank converts into.
  • intermediaryBank · string|null · optionnel
    The intermediary bank's name, where one is needed.
  • intermediarySwift · string|null · optionnel
    The intermediary bank's SWIFT/BIC.
  • intermediaryAccount · string|null · optionnel
    Our account at the intermediary bank.

  Exemple d'appel

  {"name": "admin_set_bank_transfer", "arguments": {"enabled": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_workspace_journal≈ 184 tokens

  Administrators only: what was done to one company and by whom — created, plan changed, period extended by hand, credited, suspended, resumed, erased — newest first, up to a hundred entries, each with the reason that was written down at the time. This is the answer to 'why is this company on a period nobody paid for'. The actor is our own operator, and is named because an entry without one answers nothing. A company living on another machine of the fleet is not here: the answer then names the machine to ask.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    The company's address — 'acme' in acme.kaiku.tech.

  Exemple d'appel

  {"name": "admin_workspace_journal", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• admin_workspaces≈ 366 tokens

  Administrators only: every company on the installation — its plan, what state it is in (trial, active, over-limit, suspended…), when what it paid for runs out, how many days are left, what it is using against what it may use, and its balance. Ask with endingInDays to get only the ones running out that soon, which is how 'whose trial ends this week' is answered in one call. 'attention' is the console's own short list of rows somebody has to look at. A meter reading null means the machine holding that company was not asked, not that it is idle. Owners are left out unless withOwners is true, and an e-mail address is never returned.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string|null · optionnel
    Only the company at this address ('acme' in acme.kaiku.tech).
  • status · string|null · optionnel
    Only companies in this state: 'trial', 'active', 'free', 'over-limit', 'expired', 'suspended'.
  • withOwners · boolean · optionnel
    Include who owns each company — username and display name, never an e-mail. Off by default: this is a statistics surface, and a list of customers with names on it is a customer list.
  • endingInDays · integer|null · optionnel
    Only companies whose paid-for period ends within this many days. 0 means already run out.

  Exemple d'appel

  {"name": "admin_workspaces", "arguments": {"slug": "texte", "status": "texte", "withOwners": true, "endingInDays": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• answer_issue_question≈ 282 tokens

  Answer a question that was put to you on an issue, by choosing one of its options. Only the person the question was addressed to may answer it; answering again with a different option changes the answer and says so in the thread. A question whose deadline already passed can still be answered — that replaces whatever the deadline took, and the change is recorded. The answer is written into the thread as an ordinary comment and the asker is told.

  Paramètres, retour & exemple (3)

  Paramètres

  • note · string|null · optionnel
    Words of your own beside the option — a qualification, not the answer itself ('Postgres, but only after the migration lands'). Ignored when the asker switched free text off; check 'allowsFreeText' on the question.
  • option · integer · requis
    Which option to choose, counted from 0 in the order they were offered.
  • questionId · integer · requis
    The question's id, as returned by list_issue_questions or ask_issue_question.

  Exemple d'appel

  {"name": "answer_issue_question", "arguments": {"option": 1, "questionId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• approve_wiki_page≈ 295 tokens

  Approve a wiki page IN YOUR OWN NAME, in the edition you read: 'version' is the page's version as get_wiki_page gave it, and the call is refused if the page has been edited since — read it again first. The approval is a line in the page's journal: who, when, which edition, and an optional note. It is never edited or deleted (withdraw_wiki_page_approval adds a line that takes it back). A later edit of the page does not remove it — the page then says that the edition in force is the approved one and the newer text is not approved. Only the project's lead (or the company's owner or an admin), or somebody named on the page with ask_wiki_page_approval. Approving is a person's statement: do it when your person told you to, not because a page looks finished.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · integer · requis
    Page id.
  • note · string|null · optionnel
    An optional note kept with the approval, e.g. the decision it rests on.
  • version · integer · requis
    The version you read and are approving.

  Exemple d'appel

  {"name": "approve_wiki_page", "arguments": {"id": 1, "version": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ask_issue_question≈ 568 tokens

  Ask one person a question with pre-written answer options, in an issue's thread — the way to get a decision that does not get lost in the comment stream. The question appears as an ordinary comment (so every Jira-speaking reader sees it) and is tracked separately: the person you ask sees it counted in their Questions list until they answer. It does not wait for ever — give 'defaultOption' and the deadline takes it if nobody answers, so a blocked run can go on. Requires permission to comment in that project. NOTE: this is not the bgs 'ask_question' tool, which is the background-agent ledger — this one is a question to a person on a PM issue.

  Paramètres, retour & exemple (7)

  Paramètres

  • to · string · requis
    Who to ask: the username, which list_users hands you ready-made — never the display name. They must be able to see this project, and it cannot be you.
  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • options · array · requis
    The answer options, in the order to offer them: at least 2, at most 8, each a short label rather than a paragraph. Fewer than two is not a question with options — that is a comment.
  • question · string · requis
    The question itself. Keep it to what the options answer.
  • ttlHours · integer|null · optionnel
    How long to wait, in hours. Omitted is 48 (two days). 0 means no deadline at all — the question waits until somebody answers it, which is rarely what an agent wants.
  • allowFreeText · boolean · optionnel
    Whether the answerer may add words of their own beside the option they choose. Defaults to true. Set false when the answer has to be machine-comparable and nothing else.
  • defaultOption · integer|null · optionnel
    Which option to take if nobody answers before the deadline, counted from 0. Give one whenever there is a safe assumption — it is what lets you carry on rather than stall. Omit it when no option is safe to assume: then the deadline only stops the waiting and decides nothing.

  Exemple d'appel

  {"name": "ask_issue_question", "arguments": {"to": "texte", "key": "texte", "options": [], "question": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ask_wiki_page_approval≈ 248 tokens

  Name the people who may approve a wiki page, and tell each of them: they get a notification that opens the page. 'who' is usernames or e-mails as 'a,b' — each must be able to read the page. Somebody already named is asked again, about the edition the page is at now. With release: true the people in 'who' are taken OFF the list instead; what they already approved stays approved. The project's lead, the company's owner or an admin only.

  Paramètres, retour & exemple (4)

  Paramètres

  • id · integer · requis
    Page id.
  • who · string · requis
    Usernames or e-mails, as 'a,b'. Take them from list_users.
  • note · string|null · optionnel
    A line for the people asked — what changed, by when.
  • release · boolean · optionnel
    true to take these people off the page's list instead of asking them.

  Exemple d'appel

  {"name": "ask_wiki_page_approval", "arguments": {"id": 1, "who": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_checklist_item≈ 219 tokens

  Tick or untick one checklist item by the 'id' get_checklist gave it. Written as a click on the item is: the same history line and the same notices to the issue's watchers, in your name — and only the item's box changes, so an edit somebody is saving to the description at the same moment is never lost. Ticking a ticked item changes nothing ('changed' false). An id that finds nothing means the item was rewritten or removed: read the checklist again. Requires permission to edit the issue.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    The item's id, from get_checklist.
  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • checked · boolean · optionnel
    true to tick the item, false to untick it.

  Exemple d'appel

  {"name": "check_checklist_item", "arguments": {"id": "texte", "key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• code_calls≈ 276 tokens

  Who calls a class, method or function, or what it calls, to a depth of up to 3 — each use with its file and line. Uses linked only by the bare name are counted, not listed, because they are often a different symbol of the same name. When several symbols share the name, the answer lists them to choose from.

  Paramètres, retour & exemple (5)

  Paramètres

  • path · string|null · optionnel
    The path of the symbol's file, or part of it, when its name is not enough.
  • repo · string|null · optionnel
    Which repository, as 'group/repo'. Omit to ask every repository open here.
  • depth · integer · optionnel
    How many rings out: 1 (default) to 3.
  • symbol · string · requis
    The symbol, e.g. 'IssueTransition.MoveAsync'. A bare name works when only one symbol has it.
  • direction · string|null · optionnel
    'callers' (who uses it, the default) or 'callees' (what it uses).

  Exemple d'appel

  {"name": "code_calls", "arguments": {"symbol": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• code_symbols≈ 190 tokens

  Where a class, method or function is declared in the code of the repositories connected to a project: its file, line and signature. Ask by name, or Class.Method to say whose. Only repositories whose owners opened them to agents are asked.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · requis
    The symbol's name, e.g. 'MoveAsync', or 'IssueTransition.MoveAsync' to say whose.
  • path · string|null · optionnel
    Keep only declarations in files whose path contains this.
  • repo · string|null · optionnel
    Which repository, as 'group/repo'. Omit to ask every repository open here.

  Exemple d'appel

  {"name": "code_symbols", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• connect_repository≈ 341 tokens

  Connect one more GitHub or GitLab repository to a project, by its address — 'https://github.com/owner/repo', a gitlab.com project or a company's own GitLab. No token is taken here, ever: the host is asked as anybody would ask it, so a public repository connects at once and a private one is refused, with the screen to connect it on with a token. With openSource: true it is also marked as the project's open source repository — asked without a token whether anybody can read it and under which licence — which is what set_project_public needs; marking opens nothing by itself. A repository already connected is marked rather than connected twice. Only the project's lead, a board administrator or a company admin may; the mark is written to the company's journal.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · requis
    The repository's address, e.g. 'https://github.com/owner/repo'. github.com is GitHub; any other host is taken for a GitLab.
  • openSource · boolean · optionnel
    true to mark it as this project's open source repository. Leave it out for a repository connected only for the links between issues and code.
  • projectKey · string · requis
    Key of the project, e.g. 'LIB'.

  Exemple d'appel

  {"name": "connect_repository", "arguments": {"url": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_credential≈ 537 tokens

  Attach a secret — a password, a key, a test login — to an issue or a wiki page, instead of writing it in a comment or a description, where everyone on the project reads it for ever. Pass issueKey or pageId, and a 'name' saying what it is. It can be read by the person whose token this is, by the people in 'readers', and by the project's lead, who reads every secret in the project — and by nobody else, however much of the issue they can see. The answer lists them in 'readableBy': say that to the person rather than 'only you'. There are two ways to give the value. WITHOUT 'value' nothing is stored and the answer is a 'form' link: it opens the attach dialog with the name and the readers filled in, and the person types the value there themselves. Prefer that whenever the value is not already in the conversation — a value that passes through you stays in your context and in your client's logs. WITH 'value' the secret is stored now and the answer carries its id and name, never the value; it is recorded against the token you are using. Do not repeat the value in any text you write — a comment, a description, a merge request, a log. A name in 'readers' that is unknown or cannot open the project is not stored and comes back in 'dropped' with the reason. Needs the right to edit the issue or the page.

  Paramètres, retour & exemple (5)

  Paramètres

  • name · string · requis
    What it is, e.g. 'stand admin password'. Read by everybody who may read the secret, so not the value and no part of it.
  • value · string|null · optionnel
    The secret itself. Leave it out to get a 'form' link where the person types it themselves.
  • pageId · integer|null · optionnel
    Wiki page id.
  • readers · string|null · optionnel
    Who else may read it, comma-separated usernames or emails (see list_users): 'ivan,olga'. Leave it out for nobody else.
  • issueKey · string|null · optionnel
    Issue key, e.g. 'UK-1'.

  Exemple d'appel

  {"name": "create_credential", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_issue≈ 681 tokens

  Create an issue in a project visible to this token. Returns the new issue key. Requires permission to create issues in that project. Answers with 'notified' (who this actually reaches: the people mentioned, and for an assignment the new assignee as 'assignee' and the one taken off as 'unassigned' in 'as' — never yourself) and 'unresolvedMentions' (what looked like a mention and reached nobody, each with a reason) — a wrong handle is stored as written and never refused, so that list is the only sign it did not land.

  Paramètres, retour & exemple (12)

  Paramètres

  • type · string|null · optionnel
    Issue type name, e.g. 'Task', 'Bug', 'Story', 'Epic'. Defaults to 'Task'.
  • order · integer|null · optionnel
    Its place among its parent's children: 1, 2, 3… — the order they are to be done in. Children with a place come first, in it; the rest after, by number. Filing a template's sub-tasks, pass 1, 2, 3… in turn.
  • labels · string|null · optionnel
    Labels to set, space or comma separated.
  • dueDate · string|null · optionnel
    The day this is due, as YYYY-MM-DD. A calendar day, not a timestamp — do not send a time or a zone.
  • summary · string · requis
    Issue summary (title).
  • assignee · string|null · optionnel
    Assignee username or email. Omit to leave unassigned.
  • priority · string|null · optionnel
    Priority name, e.g. 'High'.
  • teamRole · string|null · optionnel
    The project's team role this issue is for, by name, e.g. 'Звуковик' — one of the roles its administrators keep. With no assignee given, the issue goes to the person who has held that role longest.
  • parentKey · string|null · optionnel
    Parent issue key, to create this as a child/sub-task.
  • projectKey · string · requis
    Project key, e.g. 'UK'.
  • description · string|null · optionnel
    Issue description. Markdown is kept as written, and carries $…$ / $$…$$ LaTeX formulas and [~username] mentions (the username, which list_users hands you ready-made — never the display name).
  • fixVersions · string|null · optionnel
    The versions of the project this goes out in, by name, comma-separated: '2.4.0' or '2.4.0, 2.4.1' — the names list_versions gives. A name the project does not have refuses the filing and lists the ones it has.

  Exemple d'appel

  {"name": "create_issue", "arguments": {"summary": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_project≈ 644 tokens

  Administrators only: create a project — a new key, a starter board, and its own wiki space, led by you unless you name someone else. The key is yours to choose and is never invented for you: one already taken is refused, naming the project holding it, rather than quietly becoming KEY2 — the key shows in every issue key, link and commit, and renaming it later costs more than creating the project did. Calling it again with the same key and name returns that same project with created:false, so a retry after a lost answer cannot make a second project. Deleting one is not offered here: that is a decision a person makes looking at what is inside. Who may: an administrator of this workspace, or — for a subproject — the lead of the parent, since it hands over their own project's people.

  Paramètres, retour & exemple (7)

  Paramètres

  • key · string · requis
    Project key, 2–10 characters: a letter followed by letters or digits, e.g. 'BGS'. Uppercased.
  • lead · string|null · optionnel
    Username or email of the project lead. Defaults to you — a project with no lead is one nobody can configure: export, colour, the bgs connection and access grants all need a lead or an admin.
  • name · string · requis
    Project name, e.g. 'Background agents'.
  • parentKey · string|null · optionnel
    Key of the project this one is a subproject of. Everybody who may reach the parent may reach this project too, in the role they hold there — so add only the people the parent does not already have. Leave it out for a project of its own. One level: a subproject cannot have subprojects. The key here is still an ordinary key ('KYCB2B', not 'KYC-B2B'), because it is what every issue key is built from.
  • description · string|null · optionnel
    What the project is for. Markdown.
  • openSourceRepo · string|null · optionnel
    Optional: the address of the public repository this is the open source project of, e.g. 'https://github.com/owner/repo' or a GitLab project's address. The host is asked without a token whether it is public; a private or missing one refuses the project. Being open source opens nothing by itself — set_project_public does, and needs it.
  • projectTypeKey · string|null · optionnel
    Jira project type: 'software' (the default), 'business' or 'service_desk'.

  Exemple d'appel

  {"name": "create_project", "arguments": {"key": "texte", "name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_project_rule≈ 1836 tokens

  Add a rule to a project: when an issue enters 'status', append 'template' to its description. A rule appends its checklist to an issue's description when the issue ENTERS the rule's state — from the board, the Jira API or update_issue alike. The block starts with a hidden marker line '[//]: # (pm-rule:<id>)'; while that line is in the description, entering the state again adds nothing (the journal says 'alreadyThere'). A [~username] in the template is a mention: that person is notified when the checklist lands. A checklist that would make the description too long is not added and the journal says 'tooLong'; the move itself still happens. 'trigger' says WHEN: 'entered' (the default — the issue entered 'status'), 'versionReleased' (a version it goes out in was marked released), 'subtasksDone' (every issue under it is finished — the rule acts on the PARENT) or 'subtaskStarted' (an issue under it was taken into work — the parent again); or what the project's repository said through its webhook: 'branchCreated' (a branch naming the issue was made), 'mrOpened', 'mrMerged' or 'mrClosed' (a merge request — a pull request on GitHub — naming the issue was opened, merged, or closed without merging). An issue is named by its key in the branch, the title or the description, and only this project's issues are touched. 'branch' narrows the three merge-request events to a request going INTO that branch, e.g. 'main'. Nobody is behind a webhook, so such a rule acts as whoever last saved or switched it on, whatever its action. 'deployed' fires when a pipeline reports that the issue went out to an environment (report_deployment); 'environment' narrows it to one of the project's environments by name, e.g. 'staging'. 'actChanged' fires on the issues that cite a legal act when its publisher's text changed, and 'actTouched' only on those where the change is in the place they cite (or that cite the act as a whole) — found once a week, only in a project with the «Legal acts» add-on; nobody is behind a publisher either, so these act as the rule's owner too. Only 'entered' has a 'status'; pass an empty one for the others. 'fromStatus' narrows any of them to an issue coming from that state: the state it has just left for 'entered', the state it stands in for the rest. A rule with action 'move' MOVES the issue to 'moveToStatus' instead of appending anything, and has no template (pass an empty one). The move is an ordinary one — made as whoever last saved or switched on the rule, asked of the project's workflow, written to the history with the rule's name, and followed by the rules of the state it lands in. A workflow that refuses it leaves a 'moveRefused' line with the reason in the journal and nothing else; 'moved' is a move made; 'tooDeep' is a move not made because rules had already moved issues three times off one event. A rule with action 'agent' is a DUTY instead: it says which issues may be handed to an agent role (agentRole, e.g. 'product') and what the agent may do with them. Its 'template' is then the INSTRUCTION — what doing such an issue means in this project — and nothing is appended anywhere. A duty may have no state (pass an empty 'status'): then an issue is handed only by a person. agentActions is a list from: describe, subtasks, ask, wiki, report, support. agentFields names the fields it may set: priority, labels, duedate, or the project's own fields by name. doneStatus is the state it moves the issue to when done — never a finished one. capUsd raises what one task may cost, up to 5 dollars. Commenting is always allowed; finishing, deleting, reassigning and anything outside the issue never are. Saving or switching on a duty makes it yours: it runs on your behalf and access, and is switched off if you lose the project. The state and the type are NAMES of this project's own (list_project_rules lists them); an unknown one is refused with the list. Project lead or admin only.

  Paramètres, retour & exemple (18)

  Paramètres

  • name · string · requis
    What the rule is called, e.g. 'Document pack'. At most 120 characters.
  • type · string|null · optionnel
    Only issues of this type, by name, e.g. 'Bug'. Leave out for any type.
  • label · string|null · optionnel
    Only issues carrying this label (one word). Leave out for any label.
  • action · string|null · optionnel
    'checklist' (the default), 'move' to move the issue to 'moveToStatus', or 'agent' for a duty. Fixed once the rule exists.
  • branch · string|null · optionnel
    For 'mrOpened', 'mrMerged' and 'mrClosed': only a merge request going into this branch, e.g. 'main'. Leave out for any.
  • capUsd · number|null · optionnel
    For a duty: what one task may cost, in dollars, when more than the ordinary ceiling is needed. At most 5.
  • status · string · requis
    The state whose ENTRY fires the rule, by name, e.g. 'Ready for review'. For a duty taken only by hand, an empty string.
  • enabled · boolean · optionnel
    Whether the rule is on from the start. Default true.
  • trigger · string|null · optionnel
    WHEN the rule fires: 'entered' (the default), 'versionReleased', 'subtasksDone', 'subtaskStarted', or from the repository's webhook 'branchCreated', 'mrOpened', 'mrMerged', 'mrClosed', or 'deployed' when a pipeline reports a deployment, or 'actChanged' / 'actTouched' when a legal act the issue cites changed. For any but 'entered', pass an empty 'status'.
  • template · string · requis
    The checklist, as Markdown: a '### Heading' per group, '- [ ] item' per line, two spaces of indent to nest an item under another, and [~username] on an item to name who does it. For a duty: the instruction.
  • agentRole · string|null · optionnel
    For a duty: the agent role's key, e.g. 'product'.
  • doneStatus · string|null · optionnel
    For a duty: the state it moves the issue to when done. Never a finished state. Leave out and it does not move the issue.
  • fromStatus · string|null · optionnel
    Only an issue coming from this state, by name. Leave out for any.
  • projectKey · string · requis
    Project key, e.g. 'ONB'.
  • agentFields · string|null · optionnel
    For a duty: the fields it may set, comma-separated — priority, labels, duedate, or a project field's name.
  • environment · string|null · optionnel
    For 'deployed': only a deployment to this environment of the project, by name, e.g. 'staging'. Leave out for any.
  • agentActions · string|null · optionnel
    For a duty: what the agent may do beyond commenting, comma-separated — describe, subtasks, ask, wiki, report, support.
  • moveToStatus · string|null · optionnel
    For action 'move': the state the issue is moved to, by name — finished ones included.

  Exemple d'appel

  {"name": "create_project_rule", "arguments": {"name": "texte", "status": "texte", "template": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_version≈ 290 tokens

  Add a version to a project, at the end of its sequence. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue, update_issue and get_issue; JQL 'fixVersion = "2.4.0"', 'fixVersion in unreleasedVersions()'). The name is unique in its project, whatever the case. Answers with the version as list_versions gives it. Releasing it is release_version's. Project lead or admin only.

  Paramètres, retour & exemple (5)

  Paramètres

  • name · string · requis
    The version's name, e.g. '2.4.0'.
  • startDate · string|null · optionnel
    The day work on it starts, as YYYY-MM-DD.
  • projectKey · string · requis
    Project key, e.g. 'ONB'.
  • description · string|null · optionnel
    What is in it, in a sentence.
  • releaseDate · string|null · optionnel
    The day it is meant to ship, as YYYY-MM-DD.

  Exemple d'appel

  {"name": "create_version", "arguments": {"name": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_wiki_embed≈ 428 tokens

  Put one scene of a wiki page on other sites (PM-1076): a link anybody can open with no account, which plays the block's scene in our player and shows nothing else of the page — not its title, its words, its space or its author, only the 'caption' you give. Answers with the link and the ready <iframe> to paste into a site. The block is named by 'language' (anim, or anim-js where the company has scenes written in code) and its 'block' number among that kind's blocks, as get_wiki_page's 'anims' numbers them; the embed follows the block, so an edit of the scene shows everywhere. 'sites' limits which sites may frame it (https://example.org each; none is any); 'days' gives it a term (none is until removed). Only for somebody who may edit the page; it is a line in the page's history. delete_wiki_embed takes it down everywhere at once.

  Paramètres, retour & exemple (6)

  Paramètres

  • id · integer · requis
    Page id.
  • days · integer|null · optionnel
    Days the link answers, 1 to 3650. Optional: none is until it is removed.
  • block · integer · requis
    The block's number among the page's blocks of its language, from 1 — 'block' in get_wiki_page's 'anims'.
  • sites · string|null · optionnel
    Sites that may frame it, comma-separated, as https://example.org. Optional: none is any site.
  • caption · string|null · optionnel
    A line shown under the scene. Optional.
  • language · string|null · optionnel
    'anim' (default) or 'anim-js'.

  Exemple d'appel

  {"name": "create_wiki_embed", "arguments": {"id": 1, "block": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_wiki_page≈ 612 tokens

  Create a wiki page from Markdown in a space you can write to. Hangs off the space home page unless you name a parent (by 'parentId', or by 'parentTitle' within the same space). Returns the new page id and its URL. Mention someone as [@Their Name](user:username) — on a wiki page that is the form that notifies, not the [~username] used in issues; link another page as [text](page:Title) or [text](page:SPACE/Title). A ```anim block (a scene as JSON the reader's browser plays — product_help topic 'anim') is read at once: the answer's 'anims' says, per block, whether it plays or every problem with where it stands. Answers with 'notified' (who this actually reaches) and 'unresolvedMentions' (what looked like a mention and reached nobody, each with a reason) — a wrong handle is stored as written and never refused, so that list is the only sign it did not land.

  Paramètres, retour & exemple (7)

  Paramètres

  • title · string · requis
    Page title. Must be unique within the space — the title is how pages are addressed here.
  • labels · string|null · optionnel
    Labels to set, space or comma separated. Stored in lower case, except a label starting with '$', which is kept exactly as written. The label 'template' offers the page as a template: people then make pages from it.
  • markdown · string|null · optionnel
    Page body as Markdown, which also carries $…$ / $$…$$ LaTeX formulas and the wiki's macros on a line of their own — {toc}, {children}, {info} … {info}, {expand:title=…} … {expand}.
  • parentId · integer|null · optionnel
    Parent page id. Omit to hang the page off the space home page.
  • spaceKey · string · requis
    Space key, e.g. 'PM'. Every project has exactly one space, keyed like the project.
  • templateId · integer|null · optionnel
    Make the page from a template: the id of a page of the same space that carries the label 'template' (search_wiki finds them by that label). The new page starts as the template's text and its other labels; 'markdown', when you send it too, wins.
  • parentTitle · string|null · optionnel
    Parent page title, as an alternative to 'parentId'. Must be a page in the same space.

  Exemple d'appel

  {"name": "create_wiki_page", "arguments": {"title": "texte", "spaceKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• decide_join_request≈ 213 tokens

  Approve or decline one request to take part in a public project (ids from list_join_requests). Approved, the person becomes a reporter there — files issues and comments; a broader role is given on the project's people screen, as for anybody on the board. Declined, they may ask again in 14 days. The person is told by email either way, and the decision is written to the company's journal. Only the project's owner and its administrators may decide.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · integer · requis
    The request's id.
  • approve · boolean · requis
    true to let them in as a reporter, false to decline.
  • projectKey · string · requis
    Key of the public project, e.g. 'LIB'.

  Exemple d'appel

  {"name": "decide_join_request", "arguments": {"id": 1, "approve": true, "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• decide_persons≈ 267 tokens

  Confirm or reject every PROPOSED person of one source at once — the persons the reading found on one page, issue or comment. 'source' as list_persons' 'sources' names it; 'expected' is how many proposed persons of it you were shown, and if the count has changed nothing is written. Ask the person first. Members of the project who may write only. Only where the company's plan includes AI.

  Paramètres, retour & exemple (5)

  Paramètres

  • q · string|null · optionnel
    Only those with a spelling holding these words, as list_persons' 'q'.
  • state · string · requis
    'confirmed' or 'rejected'.
  • source · string · requis
    The source: 'page:471', 'issue:KYC-12', 'comment:88', 'wikicomment:7' or 'none'.
  • project · string · requis
    The project key.
  • expected · integer · requis
    How many proposed persons of the source you read in list_persons.

  Exemple d'appel

  {"name": "decide_persons", "arguments": {"state": "texte", "source": "texte", "project": "texte", "expected": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• decide_support_letter≈ 186 tokens

  Decide what a held or failed letter to the support address is. 'release' files it as if it had just arrived, past the spam filter and the limits: it joins the request it proves it answers, or opens a new one (and the sender gets the usual acknowledgement). 'dismiss' says it is not a request; its files are dropped and the row is deleted with the other unfiled letters after 30 days. Requires full write access to the support project.

  Paramètres, retour & exemple (2)

  Paramètres

  • decision · string · requis
    'release' or 'dismiss'.
  • letterId · integer · requis
    The letter's id, from list_support_letters.

  Exemple d'appel

  {"name": "decide_support_letter", "arguments": {"decision": "texte", "letterId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• decide_terms≈ 320 tokens

  Confirm or reject every PROPOSED term of one source at once — a wiki page or an issue the terms were found on — as the terms screen's «Confirm all on this page» does. Read them first with list_terms and that 'source', and pass 'expected': how many proposed terms you read there. If the count is different now (somebody decided some, or the page was read again), nothing is written and the answer says so — read the list again. Confirm only what the person asked for. Members of the project who may write only. Only where the company's plan includes AI.

  Paramètres, retour & exemple (5)

  Paramètres

  • kind · string|null · optionnel
    Only these kinds, comma-separated, as list_terms takes them.
  • state · string · requis
    'confirmed' or 'rejected'.
  • source · string · requis
    The source, as list_terms' 'sources' names it: 'page:471', 'issue:KYC-12' or 'none'.
  • project · string · requis
    The project key, e.g. KYC.
  • expected · integer · requis
    How many proposed terms of this source you read — 'total' of list_terms with state 'proposed' and this source.

  Exemple d'appel

  {"name": "decide_terms", "arguments": {"state": "texte", "source": "texte", "project": "texte", "expected": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• define_term≈ 334 tokens

  What a word means IN THIS COMPANY'S PROJECTS — a code like 'PW06' or 'F24', a project's own name for something, a notion its pages define ('петля', 'размерная подгруппа'). Ask it before guessing at a word you do not know in an issue or a page: the answer is the project's own short definition, where it is defined (a wiki page or an issue, and the heading on it) and the other ways it is written, and 'links' — the terms its definition rests on ('way': 'out', kind 'dependsOn' or 'specialCaseOf'), the ones that rest on it ('in'), and its opposites ('oppositeOf') — so a notion is read after what it rests on; term_graph has the whole picture. Matches the term or any of its spellings, case aside, then terms that begin so. Only confirmed terms, and only those whose source you may open. Empty 'terms' means the projects do not define it — then it is an ordinary word, or ask a person. Only where the company's plan includes AI.

  Paramètres, retour & exemple (2)

  Paramètres

  • word · string · requis
    The word or phrase, as you met it, e.g. 'PW06' or 'размерных подгрупп'.
  • project · string|null · optionnel
    A project key to look in it and its parent projects only. Leave out for every project you can read.

  Exemple d'appel

  {"name": "define_term", "arguments": {"word": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_agent_usage≈ 134 tokens

  Remove one agent-usage record from an issue, by the id that get_agent_usage returns. For correcting a record's numbers, re-send it with report_agent_usage instead — the same source + externalId updates in place. Requires permission to edit the issue.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer · requis
    Record id, as returned by get_agent_usage.
  • key · string · requis
    Issue key, e.g. 'UK-1'.

  Exemple d'appel

  {"name": "delete_agent_usage", "arguments": {"id": 1, "key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_attachment≈ 150 tokens

  Remove a file from an issue, by 'filename' or by attachment 'id' — both come back from get_issue. Requires permission to edit issues in that project.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · integer|null · optionnel
    Attachment id, as listed by get_issue. An alternative to 'filename'.
  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • filename · string|null · optionnel
    File name to remove, as listed by get_issue.

  Exemple d'appel

  {"name": "delete_attachment", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_computation≈ 126 tokens

  Remove one computation from an issue, by the id list_computations gives — for a job reported against the wrong issue. To correct one, report it again under its own name instead. Requires permission to edit the issue.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer · requis
    The computation's id, from list_computations.
  • key · string · requis
    Issue key, e.g. 'MATH-74'.

  Exemple d'appel

  {"name": "delete_computation", "arguments": {"id": 1, "key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_credential≈ 123 tokens

  Remove a credential, by the id from list_credentials — the value, its reader list and the record of who read it go with it, and it cannot be brought back. Only the person who attached it and the project's lead may. To take one person's access away, use update_credential's 'readers' instead.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    Credential id, from list_credentials.

  Exemple d'appel

  {"name": "delete_credential", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_issue_schedule≈ 114 tokens

  Remove a recurring issue from a project. The issues it already filed stay as they are. The project's lead, the company's owner or an admin only.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer · requis
    The schedule's id, as list_issue_schedules returned it.
  • project · string · requis
    The project key, e.g. PM.

  Exemple d'appel

  {"name": "delete_issue_schedule", "arguments": {"id": 1, "project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_person≈ 159 tokens

  Remove a person from a project's register for good, with all their spellings and facts — it cannot be undone, so do it only when the person asked for this very one to be deleted; confirm the name with them first. The journal keeps a line that a person was deleted, without the name. To turn down a PROPOSED person use set_person with state 'rejected' instead, so they are not proposed again. Members of the project who may write only.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    The person, as list_persons returned them.

  Exemple d'appel

  {"name": "delete_person", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_project_field≈ 120 tokens

  Remove a column from a project. Answers with how many issues lost a value, because that number is what the decision was about — the issues themselves are untouched. Project lead or admin only.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Field name, e.g. 'Provider'.
  • projectKey · string · requis
    Project key, e.g. 'CRM'.

  Exemple d'appel

  {"name": "delete_project_field", "arguments": {"name": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_project_issue_type≈ 117 tokens

  Remove an issue type of this project's own. Refused while any issue is of it or any field is kept for it — change those first; a rule on it goes with it. Project lead or admin only.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    The own type's name.
  • projectKey · string · requis
    Project key, e.g. 'TH'.

  Exemple d'appel

  {"name": "delete_project_issue_type", "arguments": {"name": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_project_rule≈ 132 tokens

  Remove a project rule, by its id from list_project_rules. Checklists it already added stay in their issues; its journal goes with it. To stop it for a while instead, update_project_rule with enabled=false. Project lead or admin only.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer · requis
    The rule's id, from list_project_rules.
  • projectKey · string · requis
    Project key, e.g. 'ONB'.

  Exemple d'appel

  {"name": "delete_project_rule", "arguments": {"id": 1, "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_term≈ 148 tokens

  Remove a term from its project for good — it cannot be undone or restored, so do it only when the person asked for this very term to be deleted; confirm the name with them first. To turn down a PROPOSED term use set_term with state 'rejected' instead — a rejected term is remembered and not proposed again; a deleted one may be found and proposed anew. Members of the project who may write only.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    The term, as list_terms returned it.

  Exemple d'appel

  {"name": "delete_term", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_wiki_attachment≈ 223 tokens

  Remove a file from a wiki page, by its 'filename' as listed by get_wiki_page. Identify the page by 'pageId', or by 'spaceKey' + 'title'. References to it in the page body are left alone — they simply stop resolving, so tidy the body too if it named the file. Requires permission to edit the page.

  Paramètres, retour & exemple (4)

  Paramètres

  • title · string|null · optionnel
    Exact page title, when identifying the page by title.
  • pageId · integer|null · optionnel
    Page id (as returned by search_wiki).
  • filename · string · requis
    File name to remove, as listed by get_wiki_page.
  • spaceKey · string|null · optionnel
    Space key, when identifying the page by title.

  Exemple d'appel

  {"name": "delete_wiki_attachment", "arguments": {"filename": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_wiki_embed≈ 116 tokens

  Take an embed of a wiki page's scene down (PM-1076): its link answers 404 at once on every site that has it. It cannot be undone — an embed made again of the same block gets a new link. Only for somebody who may edit the page; a line in its history.

  Paramètres, retour & exemple (1)

  Paramètres

  • embedId · integer · requis
    The embed's id, from list_wiki_embeds.

  Exemple d'appel

  {"name": "delete_wiki_embed", "arguments": {"embedId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_wiki_page≈ 222 tokens

  Delete a wiki page. Identify it by 'id', or by 'spaceKey' + 'title'. A page with children takes its whole subtree with it, so that is refused unless you pass includeChildren: true — the answer names what would go. The space home page can never be deleted. Requires permission to edit the wiki.

  Paramètres, retour & exemple (4)

  Paramètres

  • id · integer|null · optionnel
    Page id (as returned by search_wiki).
  • title · string|null · optionnel
    Exact page title, when identifying the page by title.
  • spaceKey · string|null · optionnel
    Space key, when identifying the page by title.
  • includeChildren · boolean · optionnel
    Delete the page's descendants along with it. Off by default.

  Exemple d'appel

  {"name": "delete_wiki_page", "arguments": {"id": 1, "title": "texte", "spaceKey": "texte", "includeChildren": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• distinct_persons≈ 240 tokens

  Answer a hint of list_persons' 'similar' with «these are two different people» — «Mikhailov» and «Mikhaylov» who are not one — so the pair is not hinted again; or, with 'undo', take that answer back. ASK the person first, naming both as list_persons shows them; never decide it yourself from the names. A person merged into another answers as the one they were merged into. merge_persons on such a pair still merges, and the answer goes. Both journals keep a line. Members of the project who may write only. Only where the company's plan includes AI.

  Paramètres, retour & exemple (3)

  Paramètres

  • a · integer · requis
    One of the two, as list_persons returned them.
  • b · integer · requis
    The other.
  • undo · boolean · optionnel
    true to take the answer back, so the hint may pair them again. Default false.

  Exemple d'appel

  {"name": "distinct_persons", "arguments": {"a": 1, "b": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_by_legal_document≈ 315 tokens

  Which issues and wiki pages refer to a legal act — the list on the act's card. Per document the value names (the same act in two languages is two): 'total' issue-and-place and page-and-place lines, 'hidden' of them where you may not read (counted, never named), and 'items' — the 'place' cited with the 'issue' (key, summary) or the 'page' (id, title, spaceKey). Only accepted references in projects that keep them count; a comment's reference is its issue's. Name the act by its key (e.g. 32015L0849), its address, the document id, or words of its title. The same set of issues is JQL's legalRef = "…".

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer|null · optionnel
    How many lines, at most 200. Default 50.
  • project · string|null · optionnel
    Only this project's, by its key. Omit for every project you read.
  • startAt · integer|null · optionnel
    Where to start, for a list longer than one answer.
  • document · string · requis
    The act: its key (e.g. '32015L0849'), its address, a document id, or words of its title.

  Exemple d'appel

  {"name": "find_by_legal_document", "arguments": {"document": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_issues≈ 322 tokens

  Find issues by what they are ABOUT, in plain words — by meaning as well as by words (where the server has its embedding model), so an issue that says the same thing differently or in another language is found, which search_issues (JQL) cannot do. The same search answers with `pages` (wiki pages) and `files` (PDF and Word files attached to an issue or a page, found by the words inside them): "everything on this counterparty" finds the contract and not only the issue that names it. Best first; `match` says what found each (words, meaning, or only near words — the weakest). `unread_files` lists the files this search could NOT read (a scan, a damaged or protected file, an old .doc): nothing found says nothing about those. Use search_issues for questions about fields (mine, overdue, in status X).

  Paramètres, retour & exemple (3)

  Paramètres

  • text · string · requis
    What it is about, in your own words.
  • limit · integer · optionnel
    How many of each kind to return (default 10, max 25).
  • projectKey · string|null · optionnel
    Only this project (must be visible to the token). Omit for every project the token sees.

  Exemple d'appel

  {"name": "find_issues", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_person≈ 390 tokens

  Who a name in this company's texts is — «Гупта», «N. D. Gupta», «Sjogren». Ask it BEFORE writing a person's name with initials or in another script: the answer is every person the spelling may be, each with all their spellings by script ('latin', 'cyrillic') and form ('full' — with initials or a first name, 'surname', 'inflected' — a declined form), each spelling with the source it was read from and the words there, and 'checked': 'checked' (the quote stands in its source), 'unchecked' (nobody gave a source — somebody remembered it) or 'stale' (the quote stood in its source and was edited out of it, or the source is gone: the spelling may still be right, its proof is not). Write the name as found — «Гупта (N. D. Gupta)» — and never complete initials from memory. 'ambiguous' is true when more than one person is written exactly so (two Guptas): then say which one you mean, or ask. Nothing found: add what you know with set_person, with the source and quote you read it in. Matches any spelling, case aside, then spellings that begin so. Only confirmed persons, and only spellings whose source you may open. Only where the company's plan includes AI.

  Paramètres, retour & exemple (2)

  Paramètres

  • project · string|null · optionnel
    A project key to look in it and its parent projects only. Leave out for every project you can read.
  • spelling · string · requis
    The name as you met it, e.g. 'Гупта' or 'N. D. Gupta'.

  Exemple d'appel

  {"name": "find_person", "arguments": {"spelling": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_agent_usage≈ 119 tokens

  What background-agent runs have cost an issue (local or mirrored/upstream): one record per run (tokens by kind, machine time, agent/model/host) plus the totals. A null metric means nobody reported it — which is not the same as zero, so 'reporting' says how many records carried each metric.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.

  Exemple d'appel

  {"name": "get_agent_usage", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_attachment≈ 181 tokens

  Read one file attached to an issue — its bytes, base64-encoded — by the issue key and the 'filename' as get_issue lists it. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; the pm-files MCP server saves a file to a path instead, without spending the conversation on it (local_files_setup says how to connect it). Reading needs only permission to see the issue.

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • filename · string · requis
    File name, as listed by get_issue.

  Exemple d'appel

  {"name": "get_attachment", "arguments": {"key": "texte", "filename": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_change≈ 122 tokens

  The files one merge request, pull request or commit touches, with their diffs. Large diffs arrive cut.

  Paramètres, retour & exemple (2)

  Paramètres

  • repo · string|null · optionnel
    Which repository, as 'group/repo'. Omit when only one is open.
  • change · string · requis
    The merge request or pull request number ('!12', '#12' or '12'), or a commit's hash.

  Exemple d'appel

  {"name": "get_change", "arguments": {"change": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_checklist≈ 225 tokens

  Read an issue's checklist — the '- [ ]' lines of its description — as items, in order: each with a stable 'id' (pass it to check_checklist_item), 'checked', its words ('text', without reminder or picture), its 'depth' when nested, its 'reminder' ('YYYY-MM-DD HH:MM' or null) and its 'picture' — the attachment it shows of how the item should look, with the 'content' address its bytes are read at with this same token, or null — and its 'request' when the item asks somebody for a document (a 📎 in its line): 'state' (waiting, overdue past its 'due' day, sent with a file not yet ticked, done once ticked) and the 'files' sent to it, or null for an item that asks for nothing. Needs only permission to see the issue.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.

  Exemple d'appel

  {"name": "get_checklist", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_comments≈ 291 tokens

  Read the discussion on an issue, oldest first. Without 'startAt' you get the END of the thread — the most recent 'limit' comments — because catching up means reading the latest, not the first ever written; 'earlier' says how many stand before the page you got, and 'startAt' walks back through them. Each 'body' comes back exactly as written, which is also the text update_comment's 'edits' are matched against. A reply carries 'replyTo', the id of the comment it answers (null otherwise) — pass the same id to add_comment's 'replyTo' to answer one. Comments that were deleted are not listed. Needs only permission to see the issue.

  Paramètres, retour & exemple (3)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • limit · integer · optionnel
    How many comments to return (default 20, max 100).
  • startAt · integer|null · optionnel
    Where to start, counted from the OLDEST comment as 0. Omit for the most recent page; pass 'startAt' - 'limit' from a previous answer to step back one page.

  Exemple d'appel

  {"name": "get_comments", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_issue≈ 149 tokens

  Get one issue by key (e.g. 'UK-1') if it is visible to this token, including its description, status, assignee, labels, sub-tasks, the issues it is linked to and the wiki pages linked to it. 'comments' is a COUNT, not the text — read the thread itself with get_comments whenever it is not zero: decisions, the map of what is attached and how to run the thing are often written there rather than in the description.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.

  Exemple d'appel

  {"name": "get_issue", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_legal_document≈ 377 tokens

  A legal act that issues or wiki pages you can read refer to, as it is kept here: title, publisher, 'state' (fresh, stale, waiting — named and not read yet, or unreachable), 'asOf' — the day its text is as of, how many issues and pages refer to it ('references': total, and 'hidden' of them where you may not read), its articles with their offsets ('outline', on the first look) and a window of its text, at most 12000 characters. 'changedAt' is when its words were last found changed on the publisher's site, 'editions' the earlier texts kept (from, to — the days the site was asked, not the days the act was amended — and the headings each change was under), 'failing' a site that has stopped giving it. Pass 'find' («Article 18») to land on a place, or 'offset' to read on from 'nextOffset'. Reads no site: the text is the one already read. Name the act by the document id a reference gives, by its address, or by its key (e.g. 32015L0849); an act nothing you can read refers to is not found.

  Paramètres, retour & exemple (3)

  Paramètres

  • find · string|null · optionnel
    Words to land on, e.g. 'Article 18'.
  • offset · integer|null · optionnel
    Where to read from: a previous answer's nextOffset, or an outline entry's offset.
  • document · string · requis
    The act: a document id, its address, or its key (e.g. '32015L0849').

  Exemple d'appel

  {"name": "get_legal_document", "arguments": {"document": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_project_rule_runs≈ 284 tokens

  A project rule's journal, newest first: each time an issue entered the rule's state and matched its conditions — which issue, who moved it, and the outcome: 'applied' (checklist added), 'alreadyThere' (its marker line was already in the description, nothing added) or 'tooLong' (the description would have been too long, nothing added); for a duty, 'handed' (the issue went to its agent), 'busy' (an agent already had it), 'tooMany' (the duty's fifty a day were used up) or 'refused' with a 'reason' (agent_off, agent_budget, …), and 'ownerLost' when the duty was switched off because its owner lost the project. The place to look when a checklist did not appear or an agent did not take an issue. Any member may read it.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · integer · requis
    The rule's id, from list_project_rules.
  • limit · integer · optionnel
    How many lines, newest first (default 20, max 100).
  • projectKey · string · requis
    Project key, e.g. 'ONB'.

  Exemple d'appel

  {"name": "get_project_rule_runs", "arguments": {"id": 1, "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_started≈ 265 tokens

  What this company and one of its projects could still set up in the tracker, and what is set up already — call it when the person has just started or asks what else the tracker can do. Each step has 'id', 'scope' ('company' or 'project'), 'done', 'why' (one sentence) and 'how': the next move, either an MCP 'tool' with example 'args' to call, or a 'url' of the screen to open when the step needs a token, a key or a browser — never ask for such a secret in the chat. Steps not yet done come first. Only steps the caller may take are listed: the ones that need the project's lead or the company's owner or an admin are counted in 'hidden', with a 'note' to ask them. Without 'project', the only project the caller can see is used; with several, 'projects' lists them and only the company's steps are answered.

  Paramètres, retour & exemple (1)

  Paramètres

  • project · string|null · optionnel
    The project's key, e.g. 'PM'. Optional when the caller can see only one project.

  Exemple d'appel

  {"name": "get_started", "arguments": {"project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_support_letter≈ 140 tokens

  Read one letter to the support address whole — the quoted thread and the signature that the request's comment leaves out, the HTML part as text, and the headers. 'letterId' comes from list_support_letters or from get_support_request's messages. A letter in a request is readable by whoever can read that issue; any other only by the support project's full members.

  Paramètres, retour & exemple (1)

  Paramètres

  • letterId · integer · requis
    The letter's id.

  Exemple d'appel

  {"name": "get_support_letter", "arguments": {"letterId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_support_request≈ 226 tokens

  Read who is behind a support request: the requester's name and email, whether they asked signed in (and from which workspace), their client version, what the product knew when they asked from inside it ('context': the screen, the client, the last refusal the server gave them with its request id), and which comments of the issue the requester can see ('messages', by comment id and direction; 'autoRule' names the rule when the desk's automatic answer wrote it rather than a person, 'autoWording' says whether the model worded it or the template went). Every other comment on the issue is internal — the requester never sees it. Answers found=false for an issue that is not a support request.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    Issue key of the request, e.g. 'SUPPORT-12'.

  Exemple d'appel

  {"name": "get_support_request", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_wiki_attachment≈ 299 tokens

  Read one file attached to a wiki page — its bytes, base64-encoded — identifying the page by 'pageId' or by 'spaceKey' + 'title' and the file by 'filename' as get_wiki_page lists it. This is how a file is copied from one page to another: read it here, write it with add_wiki_attachment. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; for anything larger — or for putting the file on disk — the pm-files MCP server saves it to a path instead (local_files_setup says how to connect it). Reading needs only permission to see the page.

  Paramètres, retour & exemple (4)

  Paramètres

  • title · string|null · optionnel
    Exact page title, when identifying the page by title.
  • pageId · integer|null · optionnel
    Page id (as returned by search_wiki).
  • filename · string · requis
    File name, as listed by get_wiki_page.
  • spaceKey · string|null · optionnel
    Space key, when identifying the page by title.

  Exemple d'appel

  {"name": "get_wiki_attachment", "arguments": {"filename": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_wiki_page≈ 744 tokens

  Get one wiki page by id, or by space key + title, if it is visible to this token. Returns the page text, its labels, its parent and child pages, its comments, and the issues linked to it. Pass withMarkdown: true when you intend to edit it — you then get the page's Markdown source to change and hand back to update_wiki_page, and each comment's own Markdown, version and anchor for update_wiki_comment. A large page is read a part at a time: 'outline' lists its headings and how big each section is, then 'section' returns one of them (or 'offset'/'limit' a run of lines), and update_wiki_page's 'edits' changes just the words you mean without sending the page back. A page with ```manim code blocks (where the company has scenes switched on) also returns 'scenes': each block's drawing state — queued, rendering, done or failed — manim's own error when it failed, and the attachment it was drawn into. A page with ```anim blocks (a scene as JSON the reader's client plays itself, no rendering) returns 'anims': for each, whether it can be shown, its length, or every problem with where it stands.

  Paramètres, retour & exemple (9)

  Paramètres

  • id · integer|null · optionnel
    Page id (as returned by search_wiki).
  • limit · integer|null · optionnel
    How many lines to return from 'offset' (default 200).
  • title · string|null · optionnel
    Exact page title, when looking the page up by title.
  • offset · integer|null · optionnel
    Return only the Markdown source from this 1-based line on — for a page without headings to navigate by. Pair with 'limit'.
  • outline · boolean · optionnel
    Return the page's table of contents instead of its body: per heading its level, text, anchor, the 1-based lines its section spans in the Markdown source, and its size in characters. Start here on a large page.
  • section · string|null · optionnel
    Return only this section's Markdown — its heading line down to the next heading of the same or a higher level, subsections included. Name it by its anchor (as 'outline' gives it: the id a {toc} entry links to) or by its heading text.
  • spaceKey · string|null · optionnel
    Space key, when looking the page up by title.
  • withRelated · boolean · optionnel
    With 'outline', 'section' or 'offset': also return the page's children, attachments, comments and linked issues, which a partial read otherwise leaves out.
  • withMarkdown · boolean · optionnel
    Return the Markdown source ('markdown') instead of the plain text — what to edit and pass back to update_wiki_page, and, for each comment, to update_wiki_comment. Off by default: reading costs less as text.

  Exemple d'appel

  {"name": "get_wiki_page", "arguments": {"id": 1, "limit": 1, "title": "texte", "offset": 1, "outline": true, "section": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_wiki_page_approval≈ 238 tokens

  A wiki page's APPROVAL: which edition is in force. 'version' is the edition the page is at now and 'approved' whether that very edition is approved. 'inForce' is the newest edition somebody's approval stands on — its 'version', when it was written, when it was approved and 'by' whom (null: the page was never approved). When 'inForce.version' is lower than 'version' the page was EDITED AFTER it was approved: the text you read with get_wiki_page is not the approved one. 'approvers' are the people named on the page as those who may approve it (the project's lead always may), 'canApprove' / 'canAsk' what you may do, and 'journal' every line ever written, newest first — asked, released, approved, withdrawn; no line is ever changed or removed.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    Page id (as returned by search_wiki).

  Exemple d'appel

  {"name": "get_wiki_page_approval", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_wiki_page_reading≈ 260 tokens

  A wiki page as REQUIRED READING: whether somebody is asked to read it and mark so. 'edition' is the version to read — the approved edition in force where the page has one (see get_wiki_page_approval), else the one its lead last asked about; null when the page is asked of nobody. 'required' says whether it is asked of YOU and 'readAt' when you marked that edition (absent: not yet). 'readers' is the list as written: a person, 'members' (everybody on the project) or a team role. For the project's lead there is also 'people' — everybody the page is for today, each with 'askedAt', 'readAt' and 'remindedAt' for that edition, so who has NOT read it is whoever has no 'readAt' — and 'earlier', the marks on earlier editions. A mark is on an edition: a newer approved edition leaves the old marks in 'earlier' and asks everybody again.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    Page id (as returned by search_wiki).

  Exemple d'appel

  {"name": "get_wiki_page_reading", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• link_issues≈ 314 tokens

  Link two issues: link_issues('PM-419', 'PM-417', 'is blocked by') records that PM-419 is blocked by PM-417. 'type' is the PHRASE, said as a person says it — 'blocks', 'is blocked by', 'duplicates', 'is duplicated by', 'clones', 'relates to' — so the direction is in the words and the arguments cannot disagree; a bare type name ('Blocks') points outward, as it does in Jira. A phrase this workspace does not have is REFUSED and the ones it does have are named, rather than quietly becoming 'relates to'. The link then shows on both issues (get_issue returns 'links'), and linking the same pair the same way again changes nothing. Requires permission to edit BOTH issues — a link is a change to the issue at each end.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string · requis
    The issue at the other end, e.g. 'PM-417'.
  • from · string · requis
    The issue the phrase is said about, e.g. 'PM-419'.
  • type · string · requis
    How 'from' relates to 'to', in words: 'blocks', 'is blocked by', 'duplicates', 'clones', 'relates to'. Whatever this workspace's link types call themselves — a refusal lists them.

  Exemple d'appel

  {"name": "link_issues", "arguments": {"to": "texte", "from": "texte", "type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• link_terms≈ 304 tokens

  Say how one term of a project stands to another (PM-1053): 'from' rests on 'to' ('dependsOn', the default), is a special case of it ('specialCaseOf'), or is its opposite ('oppositeOf'). 'state' 'confirmed' (the default) keeps the link — shown to readers beside the term and used for the order of reading; 'rejected' turns down a link term_graph proposed, so the definition does not offer it again; 'none' takes a link away. Terms are named by id or spelling, as term_graph returns them; 'to' must be of the project or one above it. Members of the project who may write only.

  Paramètres, retour & exemple (5)

  Paramètres

  • to · string · requis
    The term rested on: id or spelling.
  • from · string · requis
    The term that rests on the other: id or spelling.
  • kind · string|null · optionnel
    'dependsOn', 'specialCaseOf' or 'oppositeOf'. Default 'dependsOn'.
  • state · string|null · optionnel
    'confirmed', 'rejected' or 'none'. Default 'confirmed'.
  • project · string · requis
    The project key.

  Exemple d'appel

  {"name": "link_terms", "arguments": {"to": "texte", "from": "texte", "project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• link_wiki_page≈ 264 tokens

  Link a wiki page to an issue. The link then shows on both the issue and the page, and survives the page being renamed or moved. Identify the page by 'pageId', or by 'spaceKey' + 'title'. Linking the same page again updates that link instead of adding a second one. Requires permission to edit the issue.

  Paramètres, retour & exemple (5)

  Paramètres

  • title · string|null · optionnel
    Exact page title, when identifying the page by title.
  • pageId · integer|null · optionnel
    Page id (as returned by search_wiki).
  • issueKey · string · requis
    Issue key, e.g. 'UK-1'.
  • spaceKey · string|null · optionnel
    Space key, when identifying the page by title.
  • relationship · string|null · optionnel
    How the page relates to the issue, free text — e.g. 'documentation' (the default), 'specification', 'design'.

  Exemple d'appel

  {"name": "link_wiki_page", "arguments": {"issueKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_code≈ 164 tokens

  List a directory of a repository connected to a project. Only repositories whose owners opened them to agents can be read.

  Paramètres, retour & exemple (3)

  Paramètres

  • path · string|null · optionnel
    Directory inside the repository. Omit for its root.
  • repo · string|null · optionnel
    Which repository, as 'group/repo'. Its last segment alone is enough when unambiguous; omit it when only one is open.
  • reference · string|null · optionnel
    Branch, tag or commit. Omit for the default branch.

  Exemple d'appel

  {"name": "list_code", "arguments": {"path": "texte", "repo": "texte", "reference": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_computations≈ 271 tokens

  The computations issues rest on, as their runners reported them: state, progress, the commit and repository, the job's page and output, and what came of it. With 'key', one issue's; with 'projectKey', the project's, newest first and the ones still going on top — state 'open' (queued or running) is what is going now, which is the first thing to ask after a lost session instead of reading status comments. 'state' may also be one of queued, running, done, failed, cancelled, lost.

  Paramètres, retour & exemple (4)

  Paramètres

  • key · string|null · optionnel
    One issue's computations, e.g. 'MATH-74'.
  • limit · integer · optionnel
    How many, for a project (default 50, max 200).
  • state · string|null · optionnel
    Only this state, or 'open' for queued and running together.
  • projectKey · string|null · optionnel
    A project's computations, e.g. 'MATH'. Ignored when 'key' is given.

  Exemple d'appel

  {"name": "list_computations", "arguments": {"key": "texte", "limit": 1, "state": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_credentials≈ 131 tokens

  List the credentials attached to an issue or a wiki page that this token may read — names and who attached them, never the values. Pass issueKey or pageId. Use reveal_credential to read one value, and only when you are about to use it.

  Paramètres, retour & exemple (2)

  Paramètres

  • pageId · integer|null · optionnel
    Wiki page id.
  • issueKey · string|null · optionnel
    Issue key, e.g. 'UK-1'.

  Exemple d'appel

  {"name": "list_credentials", "arguments": {"pageId": 1, "issueKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_environments≈ 192 tokens

  A project's environments, in order, and its ten newest deployments. An environment is one of the places a project's work is put out to — 'dev', 'staging', 'prod' — in order; the LAST one is where finished work ends up. A deployment is a pipeline saying «this went out, there». Each issue it carried then says where it lies ('deployedTo' on get_issue), gets one history line per environment, and the project's rules with trigger 'deployed' run on it. Also 'canEdit' (you may change the list) and 'canReport' (you may report a deployment). Any member may read them.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Project key, e.g. 'ONB'.

  Exemple d'appel

  {"name": "list_environments", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_issue_questions≈ 389 tokens

  Questions with answer options, in either direction: what is waiting on YOU to answer (role='to_me'), what YOU asked and are waiting on somebody for (role='asked'), or everything on one issue. This is how you find out whether the question you asked has been answered — poll it, since ask_issue_question does not wait. With no 'key' the default is role='to_me'; with a 'key' it is every question on that issue. Open ones by default; pass state='all' for the answered, withdrawn and expired ones too.

  Paramètres, retour & exemple (5)

  Paramètres

  • key · string|null · optionnel
    Limit to one issue, e.g. 'UK-1'. Omit to look across every project this token can reach.
  • from · string|null · optionnel
    'agent' for only what an agent put to somebody (a resolution, PM-602), 'people' for only what a person asked. Omit for both.
  • role · string|null · optionnel
    Whose questions: 'to_me' (waiting on you to answer), 'asked' (you asked them, and you are waiting), or 'any'. Defaults to 'to_me' with no key, and to 'any' when a key is given.
  • limit · integer · optionnel
    How many to return (default 20, max 100).
  • state · string|null · optionnel
    'open' (the default — still waiting on somebody) or 'all', which adds the answered, the withdrawn and the expired (the deadline passed with no default and no answer).

  Exemple d'appel

  {"name": "list_issue_questions", "arguments": {"key": "texte", "from": "texte", "role": "texte", "limit": 1, "state": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_issue_schedules≈ 227 tokens

  A project's RECURRING ISSUES: issues it files by itself on a calendar — a monthly report, a quarterly review, a licence renewed every year. Each has the issue as words (summary, description, type, assignee, priority, labels), the cadence ('every' N of 'unit': week or month — 3 months is a quarter, 12 a year), 'nextDay' it files on, 'dueInDays' (the filed issue's due day, counted from the day it is filed), whose it is (it files in that person's name) and, when the last day filed nothing, 'halted' ('owner_lost': its owner can no longer configure the project and it is switched off; 'refused': the filing was refused, 'lastError' says why). 'lastIssueKey' is the last one filed. Any member may read them.

  Paramètres, retour & exemple (1)

  Paramètres

  • project · string · requis
    The project key, e.g. PM.

  Exemple d'appel

  {"name": "list_issue_schedules", "arguments": {"project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_join_requests≈ 146 tokens

  The requests of people outside the company to take part in a public project: who asked, what they wrote, when — those waiting first, then the last twenty decided. Approved, a person files issues and comments in that project and nothing else; they take no seat and see nothing else of the company. Only the project's owner and its administrators see and decide them.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Key of the public project, e.g. 'LIB'.

  Exemple d'appel

  {"name": "list_join_requests", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_legal_library≈ 152 tokens

  List the acts in the legal library — what this installation's agents have already read off the official sites: url, title, the day the text is as of (fetched_at), when the site last confirmed it (checked_at) and its length. Open where the company lets an agent role read laws.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer|null · optionnel
    How many, at most 200. Default 50.
  • filter · string|null · optionnel
    Only acts whose title or address contains this.

  Exemple d'appel

  {"name": "list_legal_library", "arguments": {"limit": 1, "filter": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_legal_references≈ 340 tokens

  The legal acts one issue or one wiki page refers to — in its own text and in the comments on it. Each reference: its 'id' (pass it to remove_legal_reference), where it stands ('in': issue, comment, page or wikiComment, with 'commentId'), the act ('document': id, url, sourceUrl, title, hasText, asOf — the day its text is as of), the 'place' cited («Article 18»), the 'quote' it was read from, 'foundBy' (url, pattern, model or hand) and 'state' — 'proposed' is the model's offer that nobody accepted yet, 'rejected' one somebody said no to. 'editionChangedAt' is set when the act's text was found changed since the reference was made and nobody has looked at it since ('editionReaches': whether the change is in the place cited, null when that cannot be told) — a person marks it looked at on the screen. 'enabled' false means the project does not keep legal references, and the list is empty. Needs only permission to see the issue or the page. In JQL and CQL the same is the field legalRef.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer|null · optionnel
    Wiki page id (as returned by search_wiki). Either this or 'issue'.
  • issue · string|null · optionnel
    Issue key, e.g. 'UK-1'. Either this or 'page'.

  Exemple d'appel

  {"name": "list_legal_references", "arguments": {"page": 1, "issue": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_mcp_connections≈ 81 tokens

  List the external MCP connections configured for a project. Auth tokens are never returned (only whether one is set).

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Project key, e.g. 'UK'.

  Exemple d'appel

  {"name": "list_mcp_connections", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_persons≈ 624 tokens

  A project's register of persons — the people its texts name — each with their spellings by script and form, each spelling's source and whether it is checked (see find_person), facts (born, died, wikidata, mathGenealogy, orcid, mrAuthor) the same way, and the project's note on why they are here. 'state' is 'confirmed', 'proposed' (found in the texts, waiting for a person — set_person with state decides it) or 'rejected'; proposed and rejected ones only to members who may write. 'reading' says whether the project has its texts read for persons. 'q' narrows to persons with a spelling holding those words. To a member who may write, 'similar' pairs two persons that look like one, with the two spellings and why — 'form' (the same up to the form of the words, «Гупта» / «Гупты»), 'letter' (one letter apart in a long Latin name, «Sjogren» / «Sjorgren»), 'transliteration' («Сьёгрен» / «Sjogren») or 'initials' («N. D. Gupta» / «Narayan D. Gupta») — a hint for the person to decide, never a fact: merge_persons only when they agree, distinct_persons when they say the two are different people — 'distinct' lists those answers. 'merged' lists the persons merged into one, whose spellings and facts are shown among its own with 'mergedFrom'. Only spellings whose source you may open; a person none of whose spellings you may see is not listed. Only where the company's plan includes AI.

  Paramètres, retour & exemple (7)

  Paramètres

  • q · string|null · optionnel
    Words a spelling holds, case aside.
  • limit · integer · optionnel
    How many to return, at most 200. Default 100.
  • state · string|null · optionnel
    'confirmed', 'proposed', 'rejected' or leave out for all you may see.
  • offset · integer · optionnel
    How many to skip — for the next page.
  • source · string|null · optionnel
    Only persons read from this source: 'page:471', 'issue:KYC-12', 'comment:88', 'wikicomment:7', or 'none' for those written with no source. 'sources' in the answer lists them with counts.
  • project · string · requis
    The project key, e.g. MATH.
  • onlyUnchecked · boolean · optionnel
    true for only persons with a spelling or fact that is not checked — written from memory or no longer in its source.

  Exemple d'appel

  {"name": "list_persons", "arguments": {"project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_project_fields≈ 100 tokens

  The columns a project keeps about its issues: name, kind, and a list's options with their colours. Also the customfield_… name each one answers to, for searching by JQL. Any member may read them.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Project key, e.g. 'CRM'.

  Exemple d'appel

  {"name": "list_project_fields", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_project_presets≈ 121 tokens

  The ready-made projects a project can take in one action — today 'requirements', a register of what a company is obliged to do: an issue type, ten columns (the norm, the obligation, who answers, what proves it, when it is reviewed), a four-state workflow, the year's recurring compliance work and two wiki page templates. Says what each brings, by name, before anything is taken.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_project_presets", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_project_rules≈ 1102 tokens

  A project's rules: when an issue enters a state, a checklist from a template is appended to its description. A rule appends its checklist to an issue's description when the issue ENTERS the rule's state — from the board, the Jira API or update_issue alike. The block starts with a hidden marker line '[//]: # (pm-rule:<id>)'; while that line is in the description, entering the state again adds nothing (the journal says 'alreadyThere'). A [~username] in the template is a mention: that person is notified when the checklist lands. A checklist that would make the description too long is not added and the journal says 'tooLong'; the move itself still happens. 'trigger' says WHEN: 'entered' (the default — the issue entered 'status'), 'versionReleased' (a version it goes out in was marked released), 'subtasksDone' (every issue under it is finished — the rule acts on the PARENT) or 'subtaskStarted' (an issue under it was taken into work — the parent again); or what the project's repository said through its webhook: 'branchCreated' (a branch naming the issue was made), 'mrOpened', 'mrMerged' or 'mrClosed' (a merge request — a pull request on GitHub — naming the issue was opened, merged, or closed without merging). An issue is named by its key in the branch, the title or the description, and only this project's issues are touched. 'branch' narrows the three merge-request events to a request going INTO that branch, e.g. 'main'. Nobody is behind a webhook, so such a rule acts as whoever last saved or switched it on, whatever its action. 'deployed' fires when a pipeline reports that the issue went out to an environment (report_deployment); 'environment' narrows it to one of the project's environments by name, e.g. 'staging'. 'actChanged' fires on the issues that cite a legal act when its publisher's text changed, and 'actTouched' only on those where the change is in the place they cite (or that cite the act as a whole) — found once a week, only in a project with the «Legal acts» add-on; nobody is behind a publisher either, so these act as the rule's owner too. Only 'entered' has a 'status'; pass an empty one for the others. 'fromStatus' narrows any of them to an issue coming from that state: the state it has just left for 'entered', the state it stands in for the rest. A rule with action 'move' MOVES the issue to 'moveToStatus' instead of appending anything, and has no template (pass an empty one). The move is an ordinary one — made as whoever last saved or switched on the rule, asked of the project's workflow, written to the history with the rule's name, and followed by the rules of the state it lands in. A workflow that refuses it leaves a 'moveRefused' line with the reason in the journal and nothing else; 'moved' is a move made; 'tooDeep' is a move not made because rules had already moved issues three times off one event. A rule with action 'agent' is a DUTY instead: it says which issues may be handed to an agent role (agentRole, e.g. 'product') and what the agent may do with them. Its 'template' is then the INSTRUCTION — what doing such an issue means in this project — and nothing is appended anywhere. A duty may have no state (pass an empty 'status'): then an issue is handed only by a person. agentActions is a list from: describe, subtasks, ask, wiki, report, support. agentFields names the fields it may set: priority, labels, duedate, or the project's own fields by name. doneStatus is the state it moves the issue to when done — never a finished one. capUsd raises what one task may cost, up to 5 dollars. Commenting is always allowed; finishing, deleting, reassigning and anything outside the issue never are. Saving or switching on a duty makes it yours: it runs on your behalf and access, and is switched off if you lose the project. Answers with each rule's id (the other rule tools take it), action, trigger, state, conditions (type, label, fromStatus, branch — null means any), template, moveToStatus and whether it is on, and for a duty its 'agent' part; with the state and type names, the triggers and the actions a rule may use, the agent roles, actions and fields a duty may name where agents are on; and 'canEdit'. Any member may read them.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Project key, e.g. 'ONB'.

  Exemple d'appel

  {"name": "list_project_rules", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_projects≈ 78 tokens

  List the projects visible to this token (a project-scoped token sees only its project). A project with a 'parent' is a subproject of that one: it has its own issues, board and wiki, and shares only who may reach it.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_projects", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_repositories≈ 173 tokens

  The GitHub and GitLab repositories a project is connected to: each one's id, host, path and address, whether it is the project's open source repository (with the licence its host named and when that was last confirmed), whether a token is set (never the token), whether agents may read its code, and whether a webhook is set. Also whether the project itself is open source and public, whether you may change the list, and the screen where a token is given. Any member may read it.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Key of the project, e.g. 'LIB'.

  Exemple d'appel

  {"name": "list_repositories", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_support_letters≈ 188 tokens

  List letters to the support address that did not become part of a request: 'held' (looked like spam, or too many at once from one address or on one request), 'failed' (we could not file them), 'ignored' (an autoresponder, a bounce, a mailing list, our own letter), 'dismissed'. Without 'state', held and failed — the ones waiting for a person. Each has an id, the reason, the sender, the subject and the file names. Only a full member of the support project may read them: they are strangers' words.

  Paramètres, retour & exemple (1)

  Paramètres

  • state · string|null · optionnel
    One of 'held', 'failed', 'ignored', 'dismissed'. Omit for held and failed.

  Exemple d'appel

  {"name": "list_support_letters", "arguments": {"state": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_support_queue≈ 331 tokens

  The support desk's queue: open requests, the most urgent first — overdue, then due soonest, then those waiting on their requester. Each item says whose turn it is ('clock.turn': 'first' = nobody has answered yet, 'reply' = the requester wrote again, 'requester' = we answered last and the clock is stopped), since when it has waited, the working hours waited, when the answer is due and whether it is 'onTime', 'dueSoon' or 'overdue'; plus the assignee. 'numbers' has the current counts and, over the last 30 days, the median time to a first human answer and to resolution (in working hours — weekdays only) and the share answered within the promise. An automatic acknowledgement or automatic answer is never counted as an answer; 'numbers.auto' says how many requests the automatic answer got, how many were then resolved with no human reply and no further word from the requester ('settled'), and how many requesters wrote again after it ('askedAgain') — per rule too. An item's 'autoRule' is set when the request got an automatic answer. Readable by anybody who can read the support project.

  Paramètres, retour & exemple (1)

  Paramètres

  • who · string|null · optionnel
    'all' (default), 'mine' (assigned to you) or 'unassigned'.

  Exemple d'appel

  {"name": "list_support_queue", "arguments": {"who": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_terms≈ 482 tokens

  A project's terms: each word, its other spellings, its short definition, its kind, and its source (a wiki page or an issue, with the heading on it). 'state' is 'confirmed' (shown to readers, marked in texts), 'proposed' (found on a page by its markup or by the model, waiting for a person — set_term with state 'confirmed' or 'rejected' decides it) or 'rejected' (kept so it is not offered again). Proposed and rejected ones are listed only to members who may write. Only terms whose source you may open. 'uses' is how many times the project's pages and issues use the term by any spelling (null: not counted yet); the most used come first, a page at a time — 'total' says how many there are. To a member who may write, 'similar' pairs a term of this page with another that looks like it up to the form of its words (plural, case) — merge_terms joins them if the person agrees. Only where the company's plan includes AI.

  Paramètres, retour & exemple (6)

  Paramètres

  • kind · string|null · optionnel
    Only these kinds, comma-separated — 'статус,система'; an empty one ('статус,') also takes terms with no kind. 'kinds' in the answer says which there are.
  • limit · integer · optionnel
    How many to return, at most 200. Default 100.
  • state · string|null · optionnel
    'confirmed', 'proposed', 'rejected' or leave out for all you may see.
  • offset · integer · optionnel
    How many to skip — for the next page.
  • source · string|null · optionnel
    Only the terms of one source — 'page:471', 'issue:KYC-12', or 'none' for the terms with no source. 'sources' in the answer says which there are, with how many.
  • project · string · requis
    The project key, e.g. KYC.

  Exemple d'appel

  {"name": "list_terms", "arguments": {"project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_tracks≈ 141 tokens

  The tracks a project is cut into: a track is a LABEL the project declared meaningful — a play, a campaign, a rollout — and work joins one by carrying that label. A track has no key of its own; its issues keep the project's key, which is what makes it a different thing from a subproject (a separate project, see create_project's parentKey). Any member may read them.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectKey · string · requis
    Project key, e.g. 'TH'.

  Exemple d'appel

  {"name": "list_tracks", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_users≈ 252 tokens

  List the people you can assign work to or mention: the members of the projects this token can see. Optionally filter by free text (username, display name or email) or narrow to one project. Mention someone in a description or comment as [~username] — a mention matches the username, never the display name — and pass the same username (or the email) as 'assignee'.

  Paramètres, retour & exemple (4)

  Paramètres

  • text · string|null · optionnel
    Free text to match in username, display name or email.
  • limit · integer · optionnel
    Max users to return (default 50, max 200).
  • projectKey · string|null · optionnel
    Restrict to members of this project key (must be visible to the token).
  • includeInactive · boolean · optionnel
    Include deactivated accounts, which can be neither assigned nor mentioned. Off by default.

  Exemple d'appel

  {"name": "list_users", "arguments": {"text": "texte", "limit": 1, "projectKey": "texte", "includeInactive": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_versions≈ 280 tokens

  A project's versions, in their sequence. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue, update_issue and get_issue; JQL 'fixVersion = "2.4.0"', 'fixVersion in unreleasedVersions()'). Each with its id, name, description, startDate and releaseDate (YYYY-MM-DD), whether it is released or archived (put away: still on its issues, no longer offered), 'overdue' (its day has passed and it has not shipped), and how many issues it carries — 'issues' — and how many of those are not finished — 'open'. Also 'canEdit': whether you may make, change and release versions here. Any member may read them.

  Paramètres, retour & exemple (2)

  Paramètres

  • projectKey · string · requis
    Project key, e.g. 'ONB'.
  • hideArchived · boolean · optionnel
    Leave out the versions that are archived. They are listed by default, since an issue may still carry one.

  Exemple d'appel

  {"name": "list_versions", "arguments": {"projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_wiki_embeds≈ 210 tokens

  The scenes of a wiki page — or of every page of a space you may edit — put on other sites (PM-1076): for each, its id, the block ('language' anim or anim-js and its number among that kind's blocks, as get_wiki_page's 'anims' numbers them), the link and the ready <iframe> code, the caption, the sites allowed to frame it (empty is any), the term ('expiresAt', null until removed), who made it and when, and how many times it was opened. Only for somebody who may edit the page; give 'id' for one page or 'spaceKey' for the space.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer|null · optionnel
    Page id. Give this or spaceKey.
  • spaceKey · string|null · optionnel
    Space key, for every page of it.

  Exemple d'appel

  {"name": "list_wiki_embeds", "arguments": {"id": 1, "spaceKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_wiki_labels≈ 114 tokens

  The labels of one wiki space with how many pages carry each, most used first — counted over the pages visible to this token. `service` marks a label that does a job rather than describe a page ('template'). search_wiki with `label` lists a label's pages.

  Paramètres, retour & exemple (1)

  Paramètres

  • spaceKey · string · requis
    The space key, e.g. 'PM'.

  Exemple d'appel

  {"name": "list_wiki_labels", "arguments": {"spaceKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_wiki_spaces≈ 51 tokens

  List the wiki spaces visible to this token. Every project has exactly one space, keyed like the project.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_wiki_spaces", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• local_files_setup≈ 168 tokens

  How the person connects pm-files — a small local MCP server that attaches files from their own computer to issues and wiki pages by path, and saves attachments back to files, so no bytes pass through the conversation. Call it when you need a local file (a screenshot, a document, anything past the base64 ceiling) and pm-files is not among your tools: hand the person the command for their client, with this workspace's address already in it. It never contains a token, and you must never ask for one — the command takes it from the person's clipboard. Changes nothing.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "local_files_setup", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• mark_wiki_page_read≈ 202 tokens

  Mark a wiki page as READ, IN YOUR OWN NAME: «I have read this edition». 'version' is the edition you read and must be the one get_wiki_page_reading gives as 'edition' — the call is refused when the edition to read is another one. Only for somebody the page is required reading for. The mark is a line in the page's journal — who, when, which edition — and is never changed or removed. It is a person's statement: make it when your person told you they have read the page, not because you fetched its text.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · integer · requis
    Page id.
  • version · integer · requis
    The edition that was read: 'edition' from get_wiki_page_reading.

  Exemple d'appel

  {"name": "mark_wiki_page_read", "arguments": {"id": 1, "version": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• merge_persons≈ 233 tokens

  Merge one person of a project's register into another when they are one human being — «Sjorgren» into «Sjogren». ASK the person first, naming both as list_persons shows them: 'similar' there is only a hint. Nothing is removed: the one merged keeps their spellings and facts with their sources, and from then on find_person, list_persons and the marks answer the other for any of their spellings. unmerge_person undoes it. Into a person already merged is into the one they were merged into; a rejected person is not merged into. Both journals keep a line. Members of the project who may write only. Only where the company's plan includes AI.

  Paramètres, retour & exemple (2)

  Paramètres

  • from · integer · requis
    The person merged, as list_persons returned them.
  • into · integer · requis
    The person who stays.

  Exemple d'appel

  {"name": "merge_persons", "arguments": {"from": 1, "into": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• merge_terms≈ 309 tokens

  Join one term to another of the same project when they are one notion — «Размерные подгруппы» into «Размерная подгруппа». The joined term's name and spellings become the target's variants (so the reading does not offer that spelling again), its links move to the target, and the joined term is gone; this cannot be undone. The target keeps its definition, kind, source and place — with 'takeDefinition', the joined term's definition replaces it, together with the source and place it was read from. The result is confirmed if either was; two proposed terms stay proposed. 'similar' in list_terms names terms that look alike up to the form of their words. Members of the project who may write only. Only where the company's plan includes AI.

  Paramètres, retour & exemple (3)

  Paramètres

  • from · integer · requis
    The term to join to the other, as list_terms returned it — it is removed.
  • into · integer · requis
    The term that stays.
  • takeDefinition · boolean · optionnel
    true to take the joined term's definition, with its source and place, instead of the target's. Default false.

  Exemple d'appel

  {"name": "merge_terms", "arguments": {"from": 1, "into": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• move_issue≈ 346 tokens

  Move an issue into another project, taking its comments, history, attachments, links and sub-tasks with it. The key does NOT change: 'PM-12' stays 'PM-12' wherever it lives, so every existing link and branch name goes on working. Call it with apply=false first (the default): the answer says what the move would cost — values in columns the target project does not have are LOST, the sprint is cleared, and a secret attached to the issue becomes readable by the target project's lead. Refuses when the target has no state by the issue's status name; say what that state becomes with 'statuses'. A sub-task cannot move on its own — move its parent. Needs full write access in BOTH projects.

  Paramètres, retour & exemple (4)

  Paramètres

  • key · string · requis
    The issue to move, e.g. 'PM-12'.
  • apply · boolean · optionnel
    false (the default) answers what the move would do and changes nothing. true does it.
  • statuses · string|null · optionnel
    What each source status becomes in the target project, as 'In Review=Review, Blocked=On hold'. Only needed for states the target does not already have under the same name.
  • toProject · string · requis
    Project key to move it into, e.g. 'CRM'.

  Exemple d'appel

  {"name": "move_issue", "arguments": {"key": "texte", "toProject": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• product_help≈ 264 tokens

  How the TRACKER ITSELF works — not what is in anybody's project: what a feature does, where it is on the screen, who may use it, and what the product does not do. Use it when the person asks about the tool ('how do sprints work here', 'where do I switch on due reminders', 'can a wiki page be restricted') rather than about their work. Without 'topic' it lists the topics, each with the questions it answers; with one it returns that topic's text. Buttons and menu items are quoted in «…» in the person's interface language — repeat them as given. 'availability' is set when the feature is switched off for this company: say that first. The text is the whole of what the help says; what it does not say, say it does not cover — do not fill it in from other trackers, and do not answer a question about the product from the project's wiki.

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string|null · optionnel
    A topic id, e.g. 'sprints'. Leave out for the list.

  Exemple d'appel

  {"name": "product_help", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• read_code≈ 158 tokens

  Read one file from a repository connected to a project. A long file arrives cut and says so; generated and binary files are not read.

  Paramètres, retour & exemple (3)

  Paramètres

  • path · string · requis
    The file's path inside the repository, e.g. 'src/app/main.ts'. Not a URL.
  • repo · string|null · optionnel
    Which repository, as 'group/repo'. Omit when only one is open.
  • reference · string|null · optionnel
    Branch, tag or commit. Omit for the default branch.

  Exemple d'appel

  {"name": "read_code", "arguments": {"path": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• release_version≈ 378 tokens

  Mark a version released — or, with released=false, take the mark back. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue, update_issue and get_issue; JQL 'fixVersion = "2.4.0"', 'fixVersion in unreleasedVersions()'). Releasing runs the project's rules that wait for a version to ship (list_project_rules, trigger 'versionReleased') on the issues it carries, and tells the project's webhooks. It does NOT refuse a version that still carries unfinished issues: 'open' in the answer says how many, and 'openIssues' names up to twenty of them — check before you release, or say so to the person. With no 'releaseDate', today is written as the day it shipped — over a planned day, as the releases screen does. Releasing a version that is already released changes nothing and answers 'already': true. Project lead or admin only.

  Paramètres, retour & exemple (4)

  Paramètres

  • version · string · requis
    The version, by its name or its id from list_versions.
  • released · boolean · optionnel
    false takes the mark back.
  • projectKey · string · requis
    Project key, e.g. 'ONB'.
  • releaseDate · string|null · optionnel
    The day it shipped, as YYYY-MM-DD. Left out, today.

  Exemple d'appel

  {"name": "release_version", "arguments": {"version": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• remove_legal_reference≈ 155 tokens

  Take a legal reference off an issue or a wiki page, by the 'id' list_legal_references gave it — as «Remove» in the block «Legal acts» does. A reference read from words that still stand in the text is kept as a «no» ('keptAsRefused' true, its state 'rejected'), so the next save does not put it back; one put by hand with no words of its own is deleted. Requires permission to edit the text it stands in.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    The reference's id, from list_legal_references.

  Exemple d'appel

  {"name": "remove_legal_reference", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• remove_track≈ 181 tokens

  Undeclare a track. THE LABEL STAYS ON THE WORK: what goes is the declaration, so the issues keep their tag and declaring the track again brings exactly the same ones back. Nothing here can lose work — but the name, icon and place ARE lost, and the track's issues count as 'outside every track' afterwards. For a track that is merely finished, archive it instead: set_track with archived=true. Needs permission to write in the project.

  Paramètres, retour & exemple (2)

  Paramètres

  • tag · string · requis
    The track's tag, e.g. 'cherry-orchard'.
  • projectKey · string · requis
    Project key, e.g. 'TH'.

  Exemple d'appel

  {"name": "remove_track", "arguments": {"tag": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reply_to_requester≈ 199 tokens

  Write to the person who opened a support request. The text becomes a comment the requester can read on their page and is emailed to them — unlike add_comment, which is always internal and never reaches the requester. Write it to the customer, in their language (get_support_request says which). Requires full write access to the support project. Answers with the comment id and whether the letter went ('emailed'; 'emailError' when it failed — the reply is kept either way).

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · requis
    Issue key of the request, e.g. 'SUPPORT-12'.
  • body · string · requis
    What to tell the requester. Markdown is kept as written.

  Exemple d'appel

  {"name": "reply_to_requester", "arguments": {"key": "texte", "body": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report_agent_usage≈ 600 tokens

  Record what one agent run cost an issue (local or mirrored/upstream): tokens by kind and machine time. Re-sending the same 'source' + 'externalId' updates that record instead of adding a second one, so a retry never doubles the spend. Omit a metric you did not measure — omitted is 'not reported', which is different from zero. Requires permission to edit the issue.

  Paramètres, retour & exemple (16)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'UK-1'.
  • host · string|null · optionnel
    Which host it ran on.
  • note · string|null · optionnel
    Short note, e.g. the outcome.
  • agent · string|null · optionnel
    Which agent did the work, e.g. 'claude-code'.
  • model · string|null · optionnel
    Which model it ran on, e.g. 'claude-opus-5'.
  • runId · string|null · optionnel
    The run this record belongs to, when one run reports several records (different models or hosts).
  • source · string · requis
    Who is reporting, e.g. 'bg-agent-api'. Idempotency is scoped to it.
  • costUsd · number|null · optionnel
    Cost in USD, if you know the rates that applied.
  • endedAt · string|null · optionnel
    When the run ended (ISO 8601).
  • startedAt · string|null · optionnel
    When the run started (ISO 8601).
  • externalId · string · requis
    Your own key for this record (usually the run id). Re-sending it updates the record.
  • inputTokens · integer|null · optionnel
    Input (prompt) tokens.
  • agentSeconds · integer|null · optionnel
    Wall-clock seconds the run took. Machine time, not a worklog.
  • outputTokens · integer|null · optionnel
    Output (completion) tokens.
  • cacheReadTokens · integer|null · optionnel
    Cache-read tokens.
  • cacheWriteTokens · integer|null · optionnel
    Cache-write tokens.

  Exemple d'appel

  {"name": "report_agent_usage", "arguments": {"key": "texte", "source": "texte", "externalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report_computation≈ 774 tokens

  Say how a computation an issue rests on stands — a GAP run, a batch of work units, a Lean build that ran somewhere else; the tracker runs nothing. Call it when the job is submitted, as it progresses and when it ends, with the same 'source' + 'externalId' every time: that is one job, updated, never a second. Send only what you know now — a field left out keeps what an earlier report said, so a progress report need not repeat the commit. 'state' is queued, running, done, failed, cancelled or lost (a job whose runner stopped answering); 'starting' reads as running. Report the commit it ran at and the repository's web address: that is what makes a [computer] result checkable, and the answer's 'commitUrl' links it where the host is GitHub or GitLab. 'result' is what came of it, in a sentence — Markdown and $…$ formulas work. Answers with 'created' and 'stateBefore'. A name already reported on another issue is refused with that issue's key. Requires permission to edit the issue.

  Paramètres, retour & exemple (15)

  Paramètres

  • key · string · requis
    The issue the computation answers, e.g. 'MATH-74'.
  • url · string|null · optionnel
    The job's own page on its runner (http/https).
  • state · string|null · optionnel
    queued, running, done, failed, cancelled or lost.
  • title · string|null · optionnel
    What it computes, in words, e.g. 'rank 5, order 2^11, stage C'.
  • commit · string|null · optionnel
    The commit it ran at.
  • result · string|null · optionnel
    What came of it, a sentence or two. Markdown, $...$ formulas.
  • source · string · requis
    Who runs it, e.g. 'tm' or 'boinc'. The job's name is unique within it.
  • command · string|null · optionnel
    How it was run: the command line or the job's description.
  • outputUrl · string|null · optionnel
    Where its output can be fetched (http/https).
  • startedAt · string|null · optionnel
    When it started (ISO 8601). Left out, a move to running stamps now.
  • externalId · string · requis
    The job's own name there, e.g. 'kimmy/gap/m74r5u'. The same name again updates the job.
  • finishedAt · string|null · optionnel
    When it ended (ISO 8601). Left out, a move to a finished state stamps now.
  • repository · string|null · optionnel
    The repository's web address, e.g. 'https://github.com/org/repo'.
  • progressDone · integer|null · optionnel
    How much is done, as the runner counts, e.g. 812.
  • progressTotal · integer|null · optionnel
    Out of how much, e.g. 1695.

  Exemple d'appel

  {"name": "report_computation", "arguments": {"key": "texte", "source": "texte", "externalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report_deployment≈ 746 tokens

  Say that something was deployed to one of a project's environments — the call a pipeline step makes. An environment is one of the places a project's work is put out to — 'dev', 'staging', 'prod' — in order; the LAST one is where finished work ends up. A deployment is a pipeline saying «this went out, there». Each issue it carried then says where it lies ('deployedTo' on get_issue), gets one history line per environment, and the project's rules with trigger 'deployed' run on it. Name the issues it carried in 'issues', or give 'from' and 'to' — two revisions — and the keys are read off the messages of the commits between them in the project's connected repository (a merge commit names its branch and merge request). Both may be given. The same 'id' for the same environment again changes nothing and answers 'repeated': true, so a step that runs twice is safe. 'version' also puts each of those issues in that version of the project. Answers with the issues it found, 'unknown' (keys you named that are no issue of this project), how many times a rule ran, and — on the project's last environment — 'unfinished': the issues that went out while not in a finished state. Needs permission to change issues in the project.

  Paramètres, retour & exemple (11)

  Paramètres

  • id · string|null · optionnel
    Your own identifier for this deployment — a pipeline or job id. Left out, 'revision' stands in for it.
  • to · string|null · optionnel
    The end of that range. Left out, 'revision'.
  • url · string|null · optionnel
    A link to the pipeline, http or https.
  • from · string|null · optionnel
    The revision the previous deployment to this environment was at — the start of the range of commits to read keys from.
  • issues · string|null · optionnel
    The issue keys it carried, comma-separated: 'ONB-12,ONB-15'.
  • version · string|null · optionnel
    A version of the project to put these issues in, by name, e.g. '2.4.0'.
  • fromLast · boolean · optionnel
    True to start the range at the revision the last deployment to this environment was reported at, instead of naming 'from'. The first report to an environment then reads no range.
  • revision · string|null · optionnel
    What went out: a commit, a tag, an image tag.
  • projectKey · string · requis
    Project key, e.g. 'ONB'.
  • repository · string|null · optionnel
    Which connected repository the range is in, as 'group/repo', when the project has several.
  • environment · string · requis
    The environment's name, e.g. 'staging' — one of list_environments.

  Exemple d'appel

  {"name": "report_deployment", "arguments": {"projectKey": "texte", "environment": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reveal_credential≈ 156 tokens

  Read one credential's value, by the id from list_credentials. This is the same act as pressing reveal on the screen and carries the same cost: it is recorded against the token you are using, and the person who owns the secret can see that you read it. Call it when you are about to use the value, not to have it on hand. The answer is marked secret: do not copy it into a comment, a description, a merge request or a log.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    Credential id, from list_credentials.

  Exemple d'appel

  {"name": "reveal_credential", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_code≈ 266 tokens

  Find where a string appears in the code of the repositories connected to a project, with the file, the line number and the lines around it. Only repositories whose owners opened them to agents are searched, and the answer says when what it searched was out of date.

  Paramètres, retour & exemple (5)

  Paramètres

  • path · string|null · optionnel
    Narrow to files whose path contains this, such as 'src/' or '.ts'.
  • repo · string|null · optionnel
    Which repository, as 'group/repo'. Omit to search every repository open here.
  • query · string · requis
    What to look for, taken literally unless regexp is set. A space is a space, not two terms.
  • regexp · boolean · optionnel
    Read query as a regular expression. One with no literal in it may not finish in time.
  • caseSensitive · boolean · optionnel
    Match case. Off by default.

  Exemple d'appel

  {"name": "search_code", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_issues≈ 1100 tokens

  Search the issues visible to this token, with a JQL query — the same JQL the Jira REST surface takes, read by the same parser. A query naming a field this tracker does not have is REFUSED and named, never run: it would match everything and read as an answer. Without `jql`, the shorthand arguments filter instead. Most recently created first unless the query says ORDER BY. Archived issues are left out unless the query names `archived`, and `archivedLeftOut` says how many matches that hid — an empty list with it is not "there are none".

  Paramètres, retour & exemple (5)

  Paramètres

  • jql · string|null · optionnel
    A JQL query, e.g. `assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC`. FIELDS: project, status, statuscategory, issuetype, type, priority, resolution, assignee, reporter, creator, key, issuekey, id, summary, description, sprint, parent, epic, labels, archived, agent, teamRole, fixVersion, fixVersions, legalRef, text, created, updated, duedate. OPERATORS: = != ~ !~ > >= < <=, IN (...), NOT IN (...), IS EMPTY, IS NOT EMPTY, combined with AND / OR, with parentheses around a sub-expression — `project = PM AND (status = Blocked OR priority = Highest)` — plus an optional trailing ORDER BY <field> [DESC]. `~` means contains (substring) and is the one to use for free text — `text` searches summary, description and comments. `>` `>=` `<` `<=` are for created/updated/duedate only, with absolute YYYY-MM-DD values: there are NO relative-date functions, so compute the date yourself. The functions are currentUser(), for assignee/reporter/creator, myTeamRoles(), for teamRole, and releasedVersions() / unreleasedVersions(), for fixVersion. `archived` is this tracker's own field: archived issues are left out unless the query mentions it. `epic` is this tracker's own too, and it is the wide one: `epic = PM-12` matches that epic AND the work under it — its children and their sub-tasks — which is how one asks for an epic's whole board in a single clause. `parent` is the narrow one: direct children only, and never the epic itself. `agent` is this tracker's own as well: `agent = product` is an issue an agent of that role has right now — working on it or waiting on its question — and `agent IS NOT EMPTY` is any agent; the assignee of such an issue is still the person it works for. `teamRole` is this tracker's own too: the project's team role an issue is for, by name — `teamRole = "Звуковик"` — and `teamRole in myTeamRoles()` is every issue for a role the caller holds, which with `assignee != currentUser()` is the work of their role that fell to somebody else. `fixVersion` is the project version an issue goes out in, by name or id — `fixVersion = "2.4.0"`; an issue may be in several, so `=` means «is in». `fixVersion in unreleasedVersions()` is what is still to ship, `fixVersion in releasedVersions(PM)` what one project has shipped, `fixVersion IS EMPTY` work in no version. `legalRef` is this tracker's own: the legal act an issue refers to, in its description or a comment — `legalRef = "32015L0849"` by the act's key, its address or its document id, `legalRef ~ "2015/849"` by words in its address or title, `legalRef IS NOT EMPTY` any act. Only in projects that keep legal references. Quote values containing spaces. Seeded values — status: Backlog, "To Do", "In Progress", "In Review", Blocked, Done; statusCategory: "To Do", "In Progress", Done; priority: Highest, High, Medium, Low, Lowest; type: Epic, Story, Task, Bug, "Sub-task". A project's own columns (PM-170) can be searched too, by name — Segment = AI — or as customfield_20003 / cf[20003]; list_project_fields names them.
  • text · string|null · optionnel
    Shorthand for `key ~ … OR summary ~ …`. Narrows the query further when `jql` is given too.
  • limit · integer · optionnel
    Max issues to return (default 25, max 100).
  • status · string|null · optionnel
    Shorthand for `status = …` (e.g. 'In Progress', 'Done'). Narrows the query further when `jql` is given too.
  • projectKey · string|null · optionnel
    Shorthand for `project = …` (must be visible to the token). Narrows the query further when `jql` is given too.

  Exemple d'appel

  {"name": "search_issues", "arguments": {"jql": "texte", "text": "texte", "limit": 1, "status": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_legal_library≈ 181 tokens

  Search the laws, regulations and standards this installation's agents have already read off the official sites (EUR-Lex, legislation.gov.uk, Fedlex, FATF and others) — by words and by meaning. Not a web search. Each hit: the act's url, title, the day its text is as of, an offset into the text and a snippet around the match. Open where the company lets an agent role read laws.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer|null · optionnel
    How many passages, at most 20. Default 8.
  • query · string · requis
    What to look for, e.g. 'beneficial owner 25% threshold'.

  Exemple d'appel

  {"name": "search_legal_library", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_wiki≈ 279 tokens

  Search wiki pages visible to this token by free text: by words in any form and by meaning (where the server has its embedding model), and literally — the title, the body, the labels written on an attached SVG diagram. Best match first; `match` says what found each page. `files` are PDF and Word files attached to pages, found by the words inside them. Optionally restrict to one space key. Without `text`, the pages most recently updated first.

  Paramètres, retour & exemple (4)

  Paramètres

  • text · string|null · optionnel
    What to look for, in your own words.
  • label · string|null · optionnel
    Only pages carrying this label (list_wiki_labels names a space's labels). With `text`, the labelled pages that say it; without, all of them, most recently updated first.
  • limit · integer · optionnel
    Max pages to return (default 25, max 100).
  • spaceKey · string|null · optionnel
    Restrict to this space key (e.g. 'PM').

  Exemple d'appel

  {"name": "search_wiki", "arguments": {"text": "texte", "label": "texte", "limit": 1, "spaceKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_environments≈ 314 tokens

  Make a project's environments exactly this list, in this order — the last is where finished work ends up. An environment is one of the places a project's work is put out to — 'dev', 'staging', 'prod' — in order; the LAST one is where finished work ends up. A deployment is a pipeline saying «this went out, there». Each issue it carried then says where it lies ('deployedTo' on get_issue), gets one history line per environment, and the project's rules with trigger 'deployed' run on it. A name the project already has is kept as it is, with what was deployed there; a name it does not have is added; and an environment LEFT OUT is removed together with the record of what was deployed to it and any rule waiting for it. So to rename one, add the new name and tell the person — there is no rename here. Project lead or admin only.

  Paramètres, retour & exemple (2)

  Paramètres

  • names · string · requis
    The environments in order, comma-separated: 'dev,staging,prod'. Each is one word of letters, digits, dots, dashes and underscores. An empty string removes them all.
  • projectKey · string · requis
    Project key, e.g. 'ONB'.

  Exemple d'appel

  {"name": "set_environments", "arguments": {"names": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_issue_fields≈ 254 tokens

  Fill in a project's own columns on one issue, by their NAMES: 'Segment=AI; Country=Poland; Started=2026-08-01', or a JSON object. A country column takes the country's name or its two-letter code. A link column takes issue keys and wiki pages (a page's address or page:471), comma-separated, and REPLACES the records you can see with them — records you cannot open stay. An empty value clears the field, which is not the same as an empty one. A value that does not fit the field's kind — an option nobody offered, a date that is not one, a country that is neither — refuses the WHOLE call rather than writing part of it.

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · requis
    Issue key, e.g. 'CRM-1'.
  • values · string · requis
    Field names to values, as 'Segment=AI; Country=Poland' or a JSON object. List values are given by option name, people by username, dates as 2026-08-21.

  Exemple d'appel

  {"name": "set_issue_fields", "arguments": {"key": "texte", "values": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_issue_schedule≈ 716 tokens

  Add a recurring issue to a project, or change the one named by 'id' — the WHOLE of it as you write it here: what you leave out of a change is cleared, not kept. From 'nextDay' on, every 'every' weeks or months, the project files this issue at nine in the morning on YOUR clock and in YOUR name: with your access, through the same rules, notifications and watchers as an issue you filed yourself. In 'summary', {date}, {month}, {quarter} and {year} are read off the day it is filed ('VAT return {quarter}' → 'VAT return Q4 2026'). If the one filed before is still open, the new one is filed all the same and linked to it. A day missed — a paused project — files once when it can, never a backlog. Refused, with the reason, if the issue could not be filed as described today (an unknown type, an assignee nobody has). The project's lead, the company's owner or an admin only.

  Paramètres, retour & exemple (13)

  Paramètres

  • id · integer|null · optionnel
    The schedule to change, as list_issue_schedules returned it. Leave out to add one.
  • type · string|null · optionnel
    Issue type name, one of the project's. 'Task' where nothing is said.
  • unit · string · optionnel
    'month' (the default) or 'week'.
  • every · integer · optionnel
    Every how many units: 1 (the default), 3 for a quarter, 12 for a year. Up to 52 weeks or 24 months.
  • labels · string|null · optionnel
    Labels as 'a,b'.
  • enabled · boolean · optionnel
    false to keep it switched off. Default true.
  • nextDay · string · requis
    The first day it files on, YYYY-MM-DD, today or later on your clock. For months, its day of the month is the day kept (the 31st is a short month's last day).
  • project · string · requis
    The project key, e.g. PM.
  • summary · string · requis
    The filed issue's title; {date}, {month}, {quarter}, {year} are filled in on the day.
  • assignee · string|null · optionnel
    Assignee username or e-mail. Nobody where nothing is said.
  • priority · string|null · optionnel
    Priority name, e.g. 'High'.
  • dueInDays · integer|null · optionnel
    The filed issue's due day, as a number of days after the day it is filed — 19 makes an issue filed on the 1st due on the 20th. A count, not a day of the month. Leave out for no due day.
  • description · string|null · optionnel
    The filed issue's description, Markdown; [~username] mentions notify each time.

  Exemple d'appel

  {"name": "set_issue_schedule", "arguments": {"nextDay": "texte", "project": "texte", "summary": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_person≈ 659 tokens

  Add a person to a project's register, or change the one named by 'id': add spellings and facts, remove them, change the name shown or the note, and confirm or reject a proposed person with 'state'. A spelling or fact given with 'source' (the page, issue or comment you READ it in: 'page:471', 'PM-12', 'comment:88', 'wikicomment:7' or an address) and 'quote' (the source's own words that hold it) is checked now, and refused if the quote is not there or does not hold it. One without a source or quote is written UNCHECKED and the answer's 'unchecked' lists it — so write a name from memory only when the person asked for it, and never invent initials. A spelling the person already has is written over with the source you give. What you leave out stays. A person written here is confirmed at once. Members of the project who may write only. Only where the company's plan includes AI.

  Paramètres, retour & exemple (9)

  Paramètres

  • id · integer|null · optionnel
    The person to change, as list_persons or find_person returned them. Leave out to add one.
  • name · string|null · optionnel
    The name shown first — one of the person's spellings, e.g. 'Гупта'; a new one becomes a spelling.
  • note · string|null · optionnel
    Why this person is here, in a line — at most 600 characters.
  • facts · string|null · optionnel
    Facts to add, as a JSON array: [{"kind":"born","value":"1938","source":"page:471","quote":"…(1938–2019)…"}]. 'kind' is born, died (a year or a date), wikidata (Q…), mathGenealogy, mrAuthor (digits) or orcid.
  • state · string|null · optionnel
    'confirmed' or 'rejected' — to decide a proposed person.
  • project · string|null · optionnel
    The project key, for a new person.
  • spellings · string|null · optionnel
    Spellings to add, as a JSON array: [{"text":"N. D. Gupta","form":"full","source":"page:471","quote":"N. D. Gupta, The dimension subgroup conjecture…","place":"Источники"}]. 'form' is 'full', 'surname' or 'inflected' (a declined form, «Гупты»); left out, it is worked out.
  • removeFacts · string|null · optionnel
    Facts to remove, as 'kind:value', comma-separated — 'born:1938'.
  • removeSpellings · string|null · optionnel
    Spellings to remove, by their text, comma-separated.

  Exemple d'appel

  {"name": "set_person", "arguments": {"id": 1, "name": "texte", "note": "texte", "facts": "texte", "state": "texte", "project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_project_field≈ 562 tokens

  Add a column to a project, or edit the one that already has this name. Keyed by name rather than by id: 'make sure there is a Segment field with these options' is the request, and a name is what you just read. A field's KIND cannot be changed once it exists. Project lead or admin only.

  Paramètres, retour & exemple (8)

  Paramètres

  • icon · string|null · optionnel
    The glyph that mark wears, from the palette list_project_fields returns. Not for a country field: that one marks a card with the flag of the country the issue holds, so passing an icon is refused rather than ignored.
  • kind · string|null · optionnel
    What it holds: 'text', 'number', 'date' (a day), 'datetime' (a day and a time, written like 2026-10-01T19:30+03:00), 'user', 'select' (a list), 'country' (a country, written as its name or its two-letter code and shown with a flag) or 'link' (issues and wiki pages, one or several — what a row is confirmed by). Required when creating; ignored when the field already exists, since a kind cannot change.
  • name · string · requis
    Field name, e.g. 'Segment'. An existing field with this name is edited rather than duplicated.
  • newName · string|null · optionnel
    Rename the field to this. Leave out to keep the name.
  • options · string|null · optionnel
    For a list: its options, as 'AI:green, Skins:orange, GameCards' or a JSON array of {name, color}. A colour is optional and must be one of: orange, amber, red, pink, purple, blue, teal, green. Options left out are REMOVED — send the whole set.
  • showIcon · boolean|null · optionnel
    Mark a board card when this field has a value: true to switch the mark on, false off. Leave out to keep it as it is.
  • issueType · string|null · optionnel
    Keep the field for issues of one type only, by name — e.g. 'Показ' — or '' for every type. Leave out to keep it as it is.
  • projectKey · string · requis
    Project key, e.g. 'CRM'.

  Exemple d'appel

  {"name": "set_project_field", "arguments": {"name": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• set_project_issue_type≈ 239 tokens

  Add an issue type of this project's own — e.g. 'Показ' — or rename one it already has. Keyed by name. The shared types (Epic, Story, Task, Bug, Sub-task, Client) are every project's and cannot be renamed here. Another project never sees this type. Project lead or admin only.

  Paramètres, retour & exemple (4)

  Paramètres

  • name · string · requis
    The type's name. An own type of this project with this name is renamed (with newName) rather than duplicated.
  • newName · string|null · optionnel
    Rename the type to this. Leave out to add or keep it.
  • subtask · boolean|null · optionnel
    When adding: true for a sub-task type, whose issues hang off a parent. Cannot be changed afterwards.
  • projectKey · string · requis
    Project key, e.g. 'TH'.

  Exemple d'appel

  {"name": "set_project_issue_type", "arguments": {"name": "texte", "projectKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

+ 23 autres outils (affichage limité à 120).

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.kaiku.tech/mcp